mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-01-05 10:20:14 +01:00
71454ae4cd
The types NMBridgeVlan, NMIPRoutingRule, NMRange, NMWireGuardPeer are immutable (or immutable, after the seal() function is called). Immutable types are great, as it means a reference to them can be shared without doing a full clone. Hence the G_DEFINE_BOXED_TYPE() for these types prefers to take a reference instead of cloning the objects. Except for sealable types, where it will prefer to clone unsealed values. Likewise, nm_simple_connection_new_clone() probably will just take another reference to the value, instead of doing a deep clone. libnm is not a thread-safe library in the sense that you could pass a NMConnection or NMClient instance to multiple threads and access them without your own synchronization. However, it should be possible that multiple threads access (seemingly) distinct objects. As the copy function of these boxed types (and nm_simple_connection_new_clone() and similar) prefers to share the references to immutable types, it is important that the ref function is thread-safe too. Otherwise you cannot just clone a NMConnection on thread1, hand the clone to thread2 and operate on the clone and the original independently. If you do before this patch, you would hit a subtle race condition. Avoid that. While atomic operations have a runtime overhead, being safe is more important. Also, we already save a full malloc()/free() by having immutable, ref-counted types. We just need to make it safe to use in order to fully benefit from it. |
||
|---|---|---|
| .. | ||
| tests | ||
| gen-metadata-nm-settings-libnm-core.c | ||
| gen-metadata-nm-settings-libnm-core.xml.in | ||
| meson.build | ||
| nm-connection-private.h | ||
| nm-connection.c | ||
| nm-default-libnm-core.h | ||
| nm-errors.c | ||
| nm-keyfile-utils.c | ||
| nm-keyfile.c | ||
| nm-meta-setting-base-impl.c | ||
| nm-property-compare.c | ||
| nm-property-compare.h | ||
| nm-setting-6lowpan.c | ||
| nm-setting-8021x.c | ||
| nm-setting-adsl.c | ||
| nm-setting-bluetooth.c | ||
| nm-setting-bond-port.c | ||
| nm-setting-bond.c | ||
| nm-setting-bridge-port.c | ||
| nm-setting-bridge.c | ||
| nm-setting-cdma.c | ||
| nm-setting-connection.c | ||
| nm-setting-dcb.c | ||
| nm-setting-dummy.c | ||
| nm-setting-ethtool.c | ||
| nm-setting-generic.c | ||
| nm-setting-gsm.c | ||
| nm-setting-hostname.c | ||
| nm-setting-infiniband.c | ||
| nm-setting-ip-config.c | ||
| nm-setting-ip-tunnel.c | ||
| nm-setting-ip4-config.c | ||
| nm-setting-ip6-config.c | ||
| nm-setting-loopback.c | ||
| nm-setting-macsec.c | ||
| nm-setting-macvlan.c | ||
| nm-setting-match.c | ||
| nm-setting-olpc-mesh.c | ||
| nm-setting-ovs-bridge.c | ||
| nm-setting-ovs-dpdk.c | ||
| nm-setting-ovs-external-ids.c | ||
| nm-setting-ovs-interface.c | ||
| nm-setting-ovs-patch.c | ||
| nm-setting-ovs-port.c | ||
| nm-setting-ppp.c | ||
| nm-setting-pppoe.c | ||
| nm-setting-private.h | ||
| nm-setting-proxy.c | ||
| nm-setting-serial.c | ||
| nm-setting-sriov.c | ||
| nm-setting-tc-config.c | ||
| nm-setting-team-port.c | ||
| nm-setting-team.c | ||
| nm-setting-tun.c | ||
| nm-setting-user.c | ||
| nm-setting-veth.c | ||
| nm-setting-vlan.c | ||
| nm-setting-vpn.c | ||
| nm-setting-vrf.c | ||
| nm-setting-vxlan.c | ||
| nm-setting-wifi-p2p.c | ||
| nm-setting-wimax.c | ||
| nm-setting-wired.c | ||
| nm-setting-wireguard.c | ||
| nm-setting-wireless-security.c | ||
| nm-setting-wireless.c | ||
| nm-setting-wpan.c | ||
| nm-setting.c | ||
| nm-simple-connection.c | ||
| nm-team-utils.c | ||
| nm-team-utils.h | ||
| nm-utils-private.h | ||
| nm-utils.c | ||
| nm-vpn-editor-plugin.c | ||
| nm-vpn-plugin-info.c | ||
| README.md | ||
libnm-core-impl
NetworkManager provides a client library libnm.
NetworkManager core does not (dynamically) link against all of libnm.
Instead, it statically links against a part of it.
That part is the static helper library libnm-core-impl.
libnm-core-impl implements (and provides) the API from
libnm-core-public, which is part of the public
API of libnm. In this form, libnm-core-impl is part
of the implementation of libnm. It also implements (and
provides) an internal API libnm-core-intern which
can only be used by those who link statically against libnm-core-impl.
Only NetworkManager core and libnm are allowed to statically
link with libnm-core-impl. Consequently, only those are allowed to include
libnm-core-intern.
This directory should not be added to the include search path of other
components as they are only allowed to include libnm-core-public
and libnm-core-intern.