Greg KH wrote: > On Sat, Oct 10, 2009 at 10:34:16AM -0700, Bryan Kadzban wrote: >> Greg KH wrote: >>> On Sat, Oct 10, 2009 at 07:47:32AM -0500, Matt Domsch wrote: >>>> On Fri, Oct 09, 2009 at 10:23:08PM -0700, Greg KH wrote: >>>>> On Fri, Oct 09, 2009 at 11:40:57PM -0500, Matt Domsch wrote: >>>>>> The fundamental roadblock to this is that enumeration != >>>>>> naming, except that it is for network devices, and we keep >>>>>> changing the enumeration order. >>>>> No, the hardware changes the enumeration order, it places >>>>> _no_ guarantees on what order stuff will be found in. So >>>>> this is not the kernel changing, just to be clear. >>>> Over time the kernel has changed its enumeration mechanisms, >>>> and introduced parallelism into the process (which is a good >>>> thing), which, from a user perspective, makes names >>>> nondeterministic. Yes, fixing this up by hard-coding MAC >>>> addresses after install has been the traditional mechanism to >>>> address this. I think there's a better way. >>> Ok, but that way can be done in userspace, without the need for >>> this char device, right? >> For the record -- when I tried to send a patch that did exactly >> this (provided an option to use by-path persistence for network >> drivers), it was rejected because "that doesn't work for USB". >> >> True, it doesn't. But by-mac (what we have today) doesn't work for >> replacing motherboards in a random home system (that can't override >> the MAC address in the BIOS), either. > > If you replace a motherboard, you honestly expect no configuration to > be needed to be changed? If so, then don't use the MAC naming scheme > for your systems. What else is there? biosdevname doesn't work with this BIOS. It looks like at least path_id has been updated to work with NICs now, so that might work, with a bit of custom rule hacking. Or at least, it won't work any more poorly than for disks, which seem to work pretty well... :-) >>> But this code is not a requirement to "solve" the fact that >>> network devices can show up in different order, that problem can >>> be solved as long as the user picks a single way to name the >>> devices, using tools that are already present today in distros. >> This code is not a requirement, no. But -- as you say -- it does >> provide a halfway-decent way to assign multiple names to a NIC. >> And that provides admins the choice to use a couple different >> persistence schemes, depending on how they expect their hardware to >> work. > > But the names need to then be resolved back to a "real" kernel name > in order to do anything with that network connection, as the char > devices are not real ones. So that adds an additional layer of > complexity on all of the system configuration tools. Yes, that is true -- and no, this change isn't perfect. But it lets me have multiple "names" per interface, and have "names" that are longer than IFNAMSIZ, though, which is why I like it. (Now, if open() would return effectively a netlink socket bound to that ifindex already, such that the program didn't need to fill in the various ifindex fields for e.g. rtnetlink... but it's probably really hard to do that, so this isn't a serious suggestion.)
Attachment:
signature.asc
Description: OpenPGP digital signature
