From: Anthony Liguori <aliguori@us.ibm.com>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: Dan Smith <danms@us.ibm.com>,
Xen Developers <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Add an ioctl interface for simple xenstore access
Date: Sat, 18 Mar 2006 11:56:27 -0600 [thread overview]
Message-ID: <441C49CB.2090308@us.ibm.com> (raw)
In-Reply-To: <20060318071405.GD23816@granada.merseine.nu>
Muli Ben-Yehuda wrote:
> On Fri, Mar 17, 2006 at 02:33:36PM -0800, Dan Smith wrote:
>
>
>> This patch adds an ioctl interface to /proc/xen/xenbus to allow simple
>> access to xenstore from domU. This patch introduces only
>> xenbus_read() support, but write, remove, etc could be easily added.
>> Also, this interface can be easily moved to /dev/xen/xenbus (or
>> something similar) later.
>>
>
> Hmm, wouldn't a virtual file system be a much better fit for xenstore
> access? the kernel community considers ioctls Evil with a capital E.
>
I'm not sure how one would express the transaction semantics of xenstore
via a virtual filesystem. 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) that makes a
filesystem non-trivial.
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.
Regards,
Anthony Liguori
> Cheers,
> Muli
>
next prev parent reply other threads:[~2006-03-18 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 22:33 [PATCH] Add an ioctl interface for simple xenstore access Dan Smith
2006-03-18 7:14 ` Muli Ben-Yehuda
2006-03-18 9:50 ` Keir Fraser
2006-03-18 18:02 ` Anthony Liguori
2006-03-18 19:32 ` Keir Fraser
2006-03-20 8:38 ` Gerd Hoffmann
2006-03-20 8:52 ` Ewan Mellor
2006-03-20 10:08 ` Keir Fraser
2006-03-20 10:10 ` Gerd Hoffmann
2006-03-18 17:56 ` Anthony Liguori [this message]
2006-03-19 0:10 ` Muli Ben-Yehuda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=441C49CB.2090308@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=danms@us.ibm.com \
--cc=mulix@mulix.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.