On Tue, Mar 30, 2010 at 20:30, Eric W. Biederman <ebiederm@xxxxxxxxxxxx> wrote: > > The main short coming of using multiple network namespaces today > is that only network devices for the primary network namespaces > can be put in the kobject layer and sysfs. > > This is essentially the earlier version of this patchset that was > reviewed before, just now on top of a version of sysfs that doesn't > need cleanup patches to support it. Just to check if we are not in conflict with planned changes, and how to possibly handle them: There is the plan and ongoing work to unify classes and buses, export them at /sys/subsystem in the same layout of the current /sys/bus/. The decision to export buses and classes as two different things (which they aren't) is the last major piece in the sysfs layout which needs to be fixed. It would mean that /sys/subsystem/net/devices/* would look like /sys/class/net/* today. But at the /sys/subsystem/net/ directory could be global network-subsystem-wide control files which would need to be namespaced too. (The network subsystem does not use subsytem-global files today, but a bunch of other classes do.) This could be modeled into the current way of doing sysfs namespaces? A /sys/bus/<subsystem>/ directory hierarchy would need to be namespaced, not just a single plain directory with symlinks. Would that work? Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
