summaryrefslogtreecommitdiff
path: root/libnm-core/nm-setting-ip6-config.c
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2018-07-28 15:26:03 +0200
committerThomas Haller <thaller@redhat.com>2018-08-10 10:38:19 +0200
commit3793804314c32b7199311736a8b1638c8f28d9fc (patch)
tree9b7261dd787b611f3c181831eb106d287aafdd19 /libnm-core/nm-setting-ip6-config.c
parent2b43ce3a940664a063f49c167abb614c241940cf (diff)
downloadNetworkManager-3793804314c32b7199311736a8b1638c8f28d9fc.tar.gz
libnm: rework setting metadata for property handling
NMSetting internally already tracked a list of all proper GObject properties and D-Bus-only properties. Rework the tracking of the list, so that: - instead of attaching the data to the GType of the setting via g_type_set_qdata(), it is tracked in a static array indexed by NMMetaSettingType. This allows to find the setting-data by simple pointer arithmetic, instead of taking a look and iterating (like g_type_set_qdata() does). Note, that this is still thread safe, because the static table entry is initialized in the class-init function with _nm_setting_class_commit(). And it only accessed by following a NMSettingClass instance, thus the class constructor already ran (maybe not for all setting classes, but for the particular one that we look up). I think this makes initialization of the metadata simpler to understand. Previously, in a first phase each class would attach the metadata to the GType as setting_property_overrides_quark(). Then during nm_setting_class_ensure_properties() it would merge them and set as setting_properties_quark(). Now, during the first phase, we only incrementally build a properties_override GArray, which we finally hand over during nm_setting_class_commit(). - sort the property infos by name and do binary search. Also expose this meta data types as internal API in nm-setting-private.h. While not accessed yet, it can prove beneficial, to have direct (internal) access to these structures. Also, rename NMSettingProperty to NMSettInfoProperty to use a distinct naming scheme. We already have 40+ subclasses of NMSetting that are called NMSetting*. Likewise, NMMetaSetting* is heavily used already. So, choose a new, distinct name.
Diffstat (limited to 'libnm-core/nm-setting-ip6-config.c')
-rw-r--r--libnm-core/nm-setting-ip6-config.c64
1 files changed, 35 insertions, 29 deletions
diff --git a/libnm-core/nm-setting-ip6-config.c b/libnm-core/nm-setting-ip6-config.c
index 3f7dd00ce0..a55fd80195 100644
--- a/libnm-core/nm-setting-ip6-config.c
+++ b/libnm-core/nm-setting-ip6-config.c
@@ -551,6 +551,7 @@ nm_setting_ip6_config_class_init (NMSettingIP6ConfigClass *klass)
{
GObjectClass *object_class = G_OBJECT_CLASS (klass);
NMSettingClass *setting_class = NM_SETTING_CLASS (klass);
+ GArray *properties_override = _nm_sett_info_property_override_create_array_ip_config ();
g_type_class_add_private (klass, sizeof (NMSettingIP6ConfigPrivate));
@@ -558,8 +559,7 @@ nm_setting_ip6_config_class_init (NMSettingIP6ConfigClass *klass)
object_class->get_property = get_property;
object_class->finalize = finalize;
- setting_class->setting_info = &nm_meta_setting_infos[NM_META_SETTING_TYPE_IP6_CONFIG];
- setting_class->verify = verify;
+ setting_class->verify = verify;
/* ---ifcfg-rh---
* property: method
@@ -888,11 +888,12 @@ nm_setting_ip6_config_class_init (NMSettingIP6ConfigClass *klass)
* description: Array of IP addresses of DNS servers (in network byte order)
* ---end---
*/
- _nm_setting_class_transform_property (setting_class,
- NM_SETTING_IP_CONFIG_DNS,
- G_VARIANT_TYPE ("aay"),
- ip6_dns_to_dbus,
- ip6_dns_from_dbus);
+ _properties_override_add_transform (properties_override,
+ g_object_class_find_property (G_OBJECT_CLASS (setting_class),
+ NM_SETTING_IP_CONFIG_DNS),
+ G_VARIANT_TYPE ("aay"),
+ ip6_dns_to_dbus,
+ ip6_dns_from_dbus);
/* ---dbus---
* property: addresses
@@ -908,12 +909,13 @@ nm_setting_ip6_config_class_init (NMSettingIP6ConfigClass *klass)
* that subnet.
* ---end---
*/
- _nm_setting_class_override_property (setting_class,
- NM_SETTING_IP_CONFIG_ADDRESSES,
- G_VARIANT_TYPE ("a(ayuay)"),
- ip6_addresses_get,
- ip6_addresses_set,
- NULL);
+ _properties_override_add_override (properties_override,
+ g_object_class_find_property (G_OBJECT_CLASS (setting_class),
+ NM_SETTING_IP_CONFIG_ADDRESSES),
+ G_VARIANT_TYPE ("a(ayuay)"),
+ ip6_addresses_get,
+ ip6_addresses_set,
+ NULL);
/* ---dbus---
* property: address-data
@@ -924,11 +926,11 @@ nm_setting_ip6_config_class_init (NMSettingIP6ConfigClass *klass)
* also exist on some addresses.
* ---end---
*/
- _nm_setting_class_add_dbus_only_property (setting_class,
- "address-data",
- G_VARIANT_TYPE ("aa{sv}"),
- ip6_address_data_get,
- ip6_address_data_set);
+ _properties_override_add_dbus_only (properties_override,
+ "address-data",
+ G_VARIANT_TYPE ("aa{sv}"),
+ ip6_address_data_get,
+ ip6_address_data_set);
/* ---dbus---
* property: routes
@@ -944,12 +946,13 @@ nm_setting_ip6_config_class_init (NMSettingIP6ConfigClass *klass)
* default metric for the device.
* ---end---
*/
- _nm_setting_class_override_property (setting_class,
- NM_SETTING_IP_CONFIG_ROUTES,
- G_VARIANT_TYPE ("a(ayuayu)"),
- ip6_routes_get,
- ip6_routes_set,
- NULL);
+ _properties_override_add_override (properties_override,
+ g_object_class_find_property (G_OBJECT_CLASS (setting_class),
+ NM_SETTING_IP_CONFIG_ROUTES),
+ G_VARIANT_TYPE ("a(ayuayu)"),
+ ip6_routes_get,
+ ip6_routes_set,
+ NULL);
/* ---dbus---
* property: route-data
@@ -964,9 +967,12 @@ nm_setting_ip6_config_class_init (NMSettingIP6ConfigClass *klass)
* also exist on some routes.
* ---end---
*/
- _nm_setting_class_add_dbus_only_property (setting_class,
- "route-data",
- G_VARIANT_TYPE ("aa{sv}"),
- ip6_route_data_get,
- ip6_route_data_set);
+ _properties_override_add_dbus_only (properties_override,
+ "route-data",
+ G_VARIANT_TYPE ("aa{sv}"),
+ ip6_route_data_get,
+ ip6_route_data_set);
+
+ _nm_setting_class_commit_full (setting_class, NM_META_SETTING_TYPE_IP6_CONFIG,
+ NULL, properties_override);
}