On 08/14/2013 02:37 PM, Cody P Schafer wrote: > Also, I'd expect userspace tools might use readdir() to find out what > memory blocks a system has (unless they just stat("memory0"), > stat("memory1")...). I don't think filesystem tricks (at least within > sysfs) are going to let this magically be solved without breaking the > userspace API. sysfs files are probably a bit too tied to kobjects to make this work easily in practice. It would probably need to be a new filesystem, imnho. But, there's nothing to keep you from creating dentries for all of the memory blocks if someone _does_ a readdir(). It'll suck, of course, but it's at least compatible with what's there. You could also 'chmod -x' it to make it more obvious that folks shouldn't be poking around in there, although it won't keep them from ls'ing. If you're concerned about resource consumption, we could also just make the directory unreadable to everyone but root. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx"> email@xxxxxxxxx </a>