All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, mingo@elte.hu, linux-mm@kvack.org,
	akpm@linux-foundation.org, hpa@zytor.com,
	gregory.haskins@gmail.com
Subject: Re: [PATCHv4 2/2] vhost_net: a kernel-level virtio server
Date: Tue, 25 Aug 2009 20:50:16 +0300	[thread overview]
Message-ID: <20090825175016.GA15790@redhat.com> (raw)
In-Reply-To: <200908252140.41295.rusty@rustcorp.com.au>

On Tue, Aug 25, 2009 at 09:40:40PM +0930, Rusty Russell wrote:
> > +	u32 __user *featurep = argp;
> > +	int __user *fdp = argp;
> > +	u32 features;
> > +	int fd, r;
> > +	switch (ioctl) {
> > +	case VHOST_NET_SET_SOCKET:
> > +		r = get_user(fd, fdp);
> > +		if (r < 0)
> > +			return r;
> > +		return vhost_net_set_socket(n, fd);
> > +	case VHOST_GET_FEATURES:
> > +		/* No features for now */
> > +		features = 0;
> > +		return put_user(features, featurep);
> 
> We may well get more than 32 feature bits, at least for virtio_net, which will
> force us to do some trickery in virtio_pci.

Unlike PCI, if we ever run out of bits we can just
add FEATURES_EXTENDED ioctl, no need for trickery.

>  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[];


Thinking about this proposal some more, how will the guest
determine the size to supply the GET_FEATURES ioctl?

Since we are a bit tight in 32 bit space already,
let's just use a 64 bit integer and be done with it?
Right?

-- 
MST

WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, mingo@elte.hu, linux-mm@kvack.org,
	akpm@linux-foundation.org, hpa@zytor.com,
	gregory.haskins@gmail.com
Subject: Re: [PATCHv4 2/2] vhost_net: a kernel-level virtio server
Date: Tue, 25 Aug 2009 20:50:16 +0300	[thread overview]
Message-ID: <20090825175016.GA15790@redhat.com> (raw)
In-Reply-To: <200908252140.41295.rusty@rustcorp.com.au>

On Tue, Aug 25, 2009 at 09:40:40PM +0930, Rusty Russell wrote:
> > +	u32 __user *featurep = argp;
> > +	int __user *fdp = argp;
> > +	u32 features;
> > +	int fd, r;
> > +	switch (ioctl) {
> > +	case VHOST_NET_SET_SOCKET:
> > +		r = get_user(fd, fdp);
> > +		if (r < 0)
> > +			return r;
> > +		return vhost_net_set_socket(n, fd);
> > +	case VHOST_GET_FEATURES:
> > +		/* No features for now */
> > +		features = 0;
> > +		return put_user(features, featurep);
> 
> We may well get more than 32 feature bits, at least for virtio_net, which will
> force us to do some trickery in virtio_pci.

Unlike PCI, if we ever run out of bits we can just
add FEATURES_EXTENDED ioctl, no need for trickery.

>  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[];


Thinking about this proposal some more, how will the guest
determine the size to supply the GET_FEATURES ioctl?

Since we are a bit tight in 32 bit space already,
let's just use a 64 bit integer and be done with it?
Right?

-- 
MST

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2009-08-25 17:55 UTC|newest]

Thread overview: 44+ 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:02 ` Michael S. Tsirkin
2009-08-19 15:02   ` Michael S. Tsirkin
2009-08-19 15:02   ` Michael S. Tsirkin
2009-08-19 15:03 ` [PATCHv4 2/2] vhost_net: a kernel-level virtio server Michael S. Tsirkin
2009-08-19 15:03   ` Michael S. Tsirkin
2009-08-19 15:03   ` Michael S. Tsirkin
2009-08-25 12:10   ` Rusty Russell
2009-08-25 12:10   ` Rusty Russell
2009-08-25 12:10     ` Rusty Russell
2009-08-25 13:16     ` Michael S. Tsirkin
2009-08-25 13:16     ` Michael S. Tsirkin
2009-08-25 13:16       ` Michael S. Tsirkin
2009-08-26 16:56       ` Michael S. Tsirkin
2009-08-26 16:56         ` Michael S. Tsirkin
2009-08-27  9:59         ` Rusty Russell
2009-08-27  9:59           ` Rusty Russell
2009-08-27  9:59         ` Rusty Russell
2009-08-26 16:56       ` Michael S. Tsirkin
2009-08-25 17:50     ` Michael S. Tsirkin
2009-08-25 17:50     ` Michael S. Tsirkin [this message]
2009-08-25 17:50       ` Michael S. Tsirkin
2009-08-26 13:40       ` Arnd Bergmann
2009-08-26 13:40         ` Arnd Bergmann
2009-08-26 13:58         ` Michael S. Tsirkin
2009-08-26 13:58         ` Michael S. Tsirkin
2009-08-26 13:58           ` Michael S. Tsirkin
2009-08-27 10:10         ` Michael S. Tsirkin
2009-08-27 10:10         ` Michael S. Tsirkin
2009-08-27 10:10           ` Michael S. Tsirkin
2009-08-27 11:03           ` Rusty Russell
2009-08-27 11:03             ` Rusty Russell
2009-08-27 11:03           ` Rusty Russell
2009-08-26 13:40       ` Arnd Bergmann
2009-08-27 10:45     ` Michael S. Tsirkin
2009-08-27 10:45     ` Michael S. Tsirkin
2009-08-27 10:45       ` Michael S. Tsirkin
2009-08-27 11:10       ` Rusty Russell
2009-08-27 11:10       ` Rusty Russell
2009-08-27 11:10         ` Rusty Russell
2009-08-27 11:19         ` Michael S. Tsirkin
2009-08-27 11:19         ` Michael S. Tsirkin
2009-08-27 11:19           ` Michael S. Tsirkin
2009-08-19 15:03 ` 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=20090825175016.GA15790@redhat.com \
    --to=mst@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregory.haskins@gmail.com \
    --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=netdev@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --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 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.