On Wed, 2010-03-31 at 07:51 +0200, Kay Sievers wrote: > On Wed, Mar 31, 2010 at 01:04, Eric W. Biederman <ebiederm@xxxxxxxxxxxx> wrote: > > Kay Sievers <kay.sievers@xxxxxxxx> writes: > >> 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. > > > > Interesting. We will symlinks ie: > > /sys/class -> /sys/subsystem > > /sys/bus -> /sys/subsystem > > to keep from breaking userspace. > > Yeah, /sys/bus/, which is the only sane layout of the needlessly > different 3 versions of the same thing (bus, class, block). [...] block vs class/block is arguable, but as for abstracting the difference between bus and class... why? Each bus defines a device interface covering enumeration, identification, power management and various aspects of their connection to the host. This interface is implemented by the bus driver. Each class defines a device interface covering functionality provided to user-space or higher level kernel components (block interface to filesystems, net driver interface to the networking core, etc). This interface is implemented by multiple device-specific drivers. So while buses and classes both define device interfaces, they are fundamentally different types of interface. And there are 'subsystems' that don't have devices at all (time, RCU, perf, ...). If you're going to expose the set of subsystems, don't they belong in there? But then, what would you put in their directories? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part
