Re: [PATCH] s390: Hypervisor File System

[Greg KH <greg@kroah.com>]

On Sat, Apr 29, 2006 at 04:41:05AM -0400, Kyle Moffett wrote:
> On Apr 29, 2006, at 03:53:11, Greg KH wrote:
> >>The update process is triggered when writing 'something' into the  
> >>'update' file at the top level hypfs directory. You can do this  
> >>e.g. with 'echo 1 > update'. During the update the whole directory  
> >>structure is deleted and built up again.
> >
> >This sounds a lot like configfs.  Why not use that instead?
> >
> >Is there a reason that sysfs can't be used for a lot of these  
> >things too?
> >
> >We already have the different cpus in sysfs, why put things in a  
> >different location than that?
> 
> It sounds like a lot of things need some kind of shell-scriptable  
> transaction interface for sysfs files.  You don't want to have more  
> than one value per file, but reading or writing of some values must  
> be done together for consistency reasons.  Is there any way to  
> implement something like this?  This would work for the framebuffer  
> people and solve the needs of a lot of the people who still want  
> ioctls or some other atomic-multivalued transfer that would otherwise  
> be a great sysfs candidate.

relayfs is for that.  You can now put relayfs files in any ram based
file system (procfs, ramfs, sysfs, debugfs, etc.)

thanks,

greg k-h