Re: [PATCHSET 3/4] sysfs: divorce sysfs from kobject and driver model

[Martin Bligh]

> The rules for sysfs files are the following:
> 	- one value, in text format, per file.
> 	- no action apon open/close
> 	- binary files are only allowed for "pass-through" type files
> 	  that the kernel does not touch (like for firmware and pci
> 	  config space)
> 	- directories should be associated with a kobject where it makes
> 	  sense (no nesting deep subdirectories without a kobject
> 	  present)
> 	- when a directory is created/removed, a uevent should happen
> 	  declaring what type of device was created/removed.

So you'll be removing:

/sys/devices/system/node/node?/meminfo

then?

along with:

/sys/devices/system/node/node?/distance
/sys/devices/system/node/node?/numastat

and all the other things that violate the rules?

(which I do agree with ... I just don't think sysfs works for
performance stats as we've discussed several times before ;-))

M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/