All of lore.kernel.org
 help / color / mirror / Atom feed
From: mdroth <mdroth@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>, Khoa Huynh <khoa@us.ibm.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Asias He <asias@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/8] configure: add CONFIG_VIRTIO_BLK_DATA_PLANE
Date: Wed, 21 Nov 2012 12:45:43 -0600	[thread overview]
Message-ID: <20121121184543.GD16281@vm> (raw)
In-Reply-To: <CAJSP0QVygfBcDJzc6-6e81mAZj-9jKhbzVrg55P=Zf6tMiUgDA@mail.gmail.com>

On Wed, Nov 21, 2012 at 07:29:21PM +0100, Stefan Hajnoczi wrote:
> On Wed, Nov 21, 2012 at 7:17 PM, mdroth <mdroth@linux.vnet.ibm.com> wrote:
> > On Tue, Nov 20, 2012 at 01:31:46PM +0100, Stefan Hajnoczi wrote:
> >> @@ -2233,6 +2238,17 @@ EOF
> >>  fi
> >>
> >>  ##########################################
> >> +# adjust virtio-blk-data-plane based on linux-aio
> >> +
> >> +if test "$virtio_blk_data_plane" = "yes" -a \
> >> +     "$linux_aio" != "yes" ; then
> >> +  echo "Error: virtio-blk-data-plane requires Linux AIO, please try --enable-linux-aio"
> >> +  exit 1
> >> +elif test -z "$virtio_blk_data_plane" ; then
> >> +  virtio_blk_data_plane=$linux_aio
> >> +fi
> >
> > $linux_aio gets set automatically if the user has libaio installed and
> > doesn't specify --disable-linux-aio, so this ends up enabling dataplane by
> > default in a lot of situations. Since it's experimental I think it should only
> > be enabled if we pass --enable-virtio-blk-data-plane explicitly.
> 
> I expect downstreams to enable this feature.  Requiring package
> maintainers to add --enable-virtio-blk-data-one explicitly is probably
> going to cause more work than any benefits of disabling it by default.
> 
> The feature has no effect unless -device
> virtio-blk-pci,x-data-plane-on is used.  Code size is <12 KB on x86_64
> and contains nothing especially risky from a security perspective.
> 
> That said, if there is a strong feeling this should be disabled by
> default, I can switch it to default off.

No, sorry for the noise. I was playing around with it locally and
noticed it enabled by default, but wasn't accounting for the fact that
you still need to enable the x-data-plane option to use it. I don't
think it hurts to compile in the support by default.

> 
> Stefan
> 

  reply	other threads:[~2012-11-21 18:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 12:31 [Qemu-devel] [PATCH v2 0/8] virtio: virtio-blk data plane Stefan Hajnoczi
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 1/8] raw-posix: add raw_get_aio_fd() for virtio-blk-data-plane Stefan Hajnoczi
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 2/8] configure: add CONFIG_VIRTIO_BLK_DATA_PLANE Stefan Hajnoczi
2012-11-21 18:17   ` mdroth
2012-11-21 18:29     ` Stefan Hajnoczi
2012-11-21 18:45       ` mdroth [this message]
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 3/8] dataplane: add host memory mapping code Stefan Hajnoczi
2012-11-20 18:24   ` Don Koch
2012-11-21  7:59     ` Stefan Hajnoczi
2012-11-26 15:31       ` Don Koch
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 4/8] dataplane: add virtqueue vring code Stefan Hajnoczi
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 5/8] dataplane: add event loop Stefan Hajnoczi
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 6/8] dataplane: add Linux AIO request queue Stefan Hajnoczi
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 7/8] dataplane: add virtio-blk data plane code Stefan Hajnoczi
2012-11-20 13:04   ` Michael S. Tsirkin
2012-11-20 13:54     ` Stefan Hajnoczi
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 8/8] virtio-blk: add x-data-plane=on|off performance feature Stefan Hajnoczi
2012-11-20 12:37   ` Daniel P. Berrange
2012-11-20 12:53     ` Kevin Wolf
2012-11-20 13:50     ` Stefan Hajnoczi
2012-11-20 14:34       ` Daniel P. Berrange

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=20121121184543.GD16281@vm \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=asias@redhat.com \
    --cc=khoa@us.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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.