Add support to use create_named_child() in NetworkManager to allow custom naming of 'Pkey-ed' devices.
Description of the feature
In the current scenario, NM brings up the Pey-ed devices and names them as NAME=(PHYSDEV).
((0x8000 | $PKEY_ID))
They do not allow for the custom naming of the pkey-ed devices and thus the names of these devices are tightly coupled with the PKEY.
An upstream commit was filed to introduce the kernel support required to do this by adding a new function called create_named_child() [reference 1]. This adds the necessary kernel support to decouple the names from the pkey for these devices and support custom names.
I would like to make a feature request to enhance NetworkManager to utilize create_named_child() to add support for custom naming of Pkey-ed devices.
NetworkManager version: NetworkManager-1.40.16-9.0.1.el8.x86_64
Description of the use cases
The Pkey-ed device names can change (as they are derived from the Pkeys) as the pkeys change. This makes administration of these devices difficult.We use these pkey-ed devices on our internal machines and would like to use custom names to make administration of these devices more consistent.