On Sat, Mar 18, 2006 at 11:56:27AM -0600, Anthony Liguori wrote:
> I'm not sure how one would express the transaction semantics of xenstore
> via a virtual filesystem.
file open - transaction begin, file close - transaction commit, if you
need multiple "files" in a single transaction, you make this a special
file. Not very elegant, but as plan9 shows us, nearly anything can be
represented as a file{system}.
> There is also an awkward mapping between some
> of the attributes of xenstore (for instance, there's no way to determine
> if an attribute returned by a list is a directory or not)
If it has "sub attributes", represent it as a directory.
> If you remember, I had written a fuse filesystem front-end for xenstore
> at one point. It's definitely neat, but I think we would have to make
> some changes to Xenstore for it to really work out well.
Ok. I freely acknowledge knowing very little about xenstore and how to
best represent its data. I do however know what the review comments
for upstream inclusion of any new ioctls would be like ;-)
Cheers,
Muli
--
Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home