From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, hpa@zytor.com, mingo@elte.hu,
akpm@linux-foundation.org
Subject: Re: [PATCHv4 2/2] vhost_net: a kernel-level virtio server
Date: Thu, 27 Aug 2009 20:33:26 +0930 [thread overview]
Message-ID: <200908272033.26540.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090827101026.GA8545@redhat.com>
On Thu, 27 Aug 2009 07:40:26 pm Michael S. Tsirkin wrote:
> On Wed, Aug 26, 2009 at 03:40:59PM +0200, Arnd Bergmann wrote:
> > On Tuesday 25 August 2009, Michael S. Tsirkin wrote:
> > > > I'd like to avoid that here,
> > > > though it's kind of ugly. We'd need VHOST_GET_FEATURES (and ACK) to take a
> > > > struct like:
> > > >
> > > > u32 feature_size;
> > > > u32 features[];
> >
> > Hmm, variable length ioctl arguments, I'd rather not go there.
> > The ioctl infrastructure already has a length argument encoded
> > in the ioctl number. We can use that if we need more, e.g.
> >
> > /* now */
> > #define VHOST_GET_FEATURES _IOR(VHOST_VIRTIO, 0x00, __u64)
> > /*
> > * uncomment if we run out of feature bits:
> >
> > struct vhost_get_features2 {
> > __u64 bits[2];
> > };
> > #define VHOST_GET_FEATURES2 _IOR(VHOST_VIRTIO, 0x00, \
> > struct vhost_get_features2)
> > */
>
>
> I thought so, too. Rusty, agree?
Yep, am convinced. Make it u64 to stop us having to do this tomorrow, then
we can always extend later.
Thanks,
Rusty.
next prev parent reply other threads:[~2009-08-27 11:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1250693417.git.mst@redhat.com>
2009-08-19 15:02 ` [PATCHv4 1/2] mm: export use_mm/unuse_mm to modules Michael S. Tsirkin
2009-08-19 15:03 ` [PATCHv4 2/2] vhost_net: a kernel-level virtio server Michael S. Tsirkin
2009-08-25 12:10 ` Rusty Russell
2009-08-25 13:16 ` Michael S. Tsirkin
2009-08-26 16:56 ` Michael S. Tsirkin
2009-08-27 9:59 ` Rusty Russell
2009-08-25 17:50 ` Michael S. Tsirkin
2009-08-26 13:40 ` Arnd Bergmann
2009-08-26 13:58 ` Michael S. Tsirkin
2009-08-27 10:10 ` Michael S. Tsirkin
2009-08-27 11:03 ` Rusty Russell [this message]
2009-08-27 10:45 ` Michael S. Tsirkin
2009-08-27 11:10 ` Rusty Russell
2009-08-27 11:19 ` Michael S. Tsirkin
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=200908272033.26540.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).