From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
anthony@codemonkey.ws, jes.sorensen@redhat.com
Subject: Re: [PATCH 5/5] virtio-net: Switch default to new bottom half TX handler for iothread
Date: Wed, 1 Sep 2010 11:47:00 +0300 [thread overview]
Message-ID: <20100901084700.GA6136@redhat.com> (raw)
In-Reply-To: <1283293974.5826.154.camel@x201>
On Tue, Aug 31, 2010 at 04:32:54PM -0600, Alex Williamson wrote:
> On Tue, 2010-08-31 at 23:25 +0300, Michael S. Tsirkin wrote:
> > On Fri, Aug 27, 2010 at 04:37:45PM -0600, Alex Williamson wrote:
> > > The bottom half handler shows big improvements over the timer
> > > with few downsides, default to it when the iothread is enabled.
> > >
> > > Using the following tests, with the guest and host connected
> > > via tap+bridge:
> > >
> > > guest> netperf -t TCP_STREAM -H $HOST
> > > host> netperf -t TCP_STREAM -H $GUEST
> > > guest> netperf -t UDP_STREAM -H $HOST
> > > host> netperf -t UDP_STREAM -H $GUEST
> > > guest> netperf -t TCP_RR -H $HOST
> > >
> > > Results: base throughput, exits/throughput ->
> > > patched throughput, exits/throughput
> > >
> > > --enable-io-thread
> > > TCP guest->host 2737.77, 47.82 -> 6767.09, 29.15 = 247%, 61%
> > > TCP host->guest 2231.33, 74.00 -> 4125.80, 67.61 = 185%, 91%
> > > UDP guest->host 6281.68, 14.66 -> 12569.27, 1.98 = 200%, 14%
> > > UDP host->guest 275.91, 289.22 -> 264.80, 293.53 = 96%, 101%
> > > interations/s 1949.65, 82.97 -> 7417.56, 84.31 = 380%, 102%
> > >
> > > No --enable-io-thread
> > > TCP guest->host 3041.57, 55.11 -> 1038.93, 517.57 = 34%, 939%
> > > TCP host->guest 2416.03, 76.67 -> 5655.92, 55.52 = 234%, 72%
> > > UDP guest->host 12255.82, 6.11 -> 7775.87, 31.32 = 63%, 513%
> > > UDP host->guest 587.92, 245.95 -> 611.88, 239.92 = 104%, 98%
> > > interations/s 1975.59, 83.21 -> 8935.50, 88.18 = 452%, 106%
> > >
> > > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> >
> > parameter having different settings based on config
> > options might surprise some users. I don't think
> > we really need a parameter here ...
>
> I'm not a bit fan of this either, but I'd also prefer not to introduce a
> regression for a performance difference we know about in advance.
I agree. The comment was mainly about a parameter. If we make it a hidden
parameter (mainbe with x- prefix), this won't be an issue.
> It gets even more complicated when we factor in qemu-kvm, as it doesn't
> build with iothread enabled, but seems to get and even better boost in
> performance across the board thanks largely to the kvm-irqchip. Should
> we instead make this a configure option? --enable-virtio-net-txbh?
That'll work too.
> Thanks,
>
> Alex
>
> > > ---
> > >
> > > hw/s390-virtio-bus.c | 3 ++-
> > > hw/syborg_virtio.c | 3 ++-
> > > hw/virtio-pci.c | 3 ++-
> > > hw/virtio.h | 6 ++++++
> > > 4 files changed, 12 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/hw/s390-virtio-bus.c b/hw/s390-virtio-bus.c
> > > index 1483362..985f99a 100644
> > > --- a/hw/s390-virtio-bus.c
> > > +++ b/hw/s390-virtio-bus.c
> > > @@ -328,7 +328,8 @@ static VirtIOS390DeviceInfo s390_virtio_net = {
> > > .qdev.size = sizeof(VirtIOS390Device),
> > > .qdev.props = (Property[]) {
> > > DEFINE_NIC_PROPERTIES(VirtIOS390Device, nic),
> > > - DEFINE_PROP_UINT32("txtimer", VirtIOS390Device, txtimer, 1),
> > > + DEFINE_PROP_UINT32("txtimer", VirtIOS390Device, txtimer,
> > > + TXTIMER_DEFAULT),
> > > DEFINE_PROP_INT32("txburst", VirtIOS390Device, txburst, 256),
> > > DEFINE_PROP_END_OF_LIST(),
> > > },
> > > diff --git a/hw/syborg_virtio.c b/hw/syborg_virtio.c
> > > index 7b76972..ee5746d 100644
> > > --- a/hw/syborg_virtio.c
> > > +++ b/hw/syborg_virtio.c
> > > @@ -300,7 +300,8 @@ static SysBusDeviceInfo syborg_virtio_net_info = {
> > > .qdev.props = (Property[]) {
> > > DEFINE_NIC_PROPERTIES(SyborgVirtIOProxy, nic),
> > > DEFINE_VIRTIO_NET_FEATURES(SyborgVirtIOProxy, host_features),
> > > - DEFINE_PROP_UINT32("txtimer", SyborgVirtIOProxy, txtimer, 1),
> > > + DEFINE_PROP_UINT32("txtimer", SyborgVirtIOProxy, txtimer,
> > > + TXTIMER_DEFAULT),
> > > DEFINE_PROP_INT32("txburst", SyborgVirtIOProxy, txburst, 256),
> > > DEFINE_PROP_END_OF_LIST(),
> > > }
> > > diff --git a/hw/virtio-pci.c b/hw/virtio-pci.c
> > > index e025c09..9740f57 100644
> > > --- a/hw/virtio-pci.c
> > > +++ b/hw/virtio-pci.c
> > > @@ -695,7 +695,8 @@ static PCIDeviceInfo virtio_info[] = {
> > > DEFINE_PROP_UINT32("vectors", VirtIOPCIProxy, nvectors, 3),
> > > DEFINE_VIRTIO_NET_FEATURES(VirtIOPCIProxy, host_features),
> > > DEFINE_NIC_PROPERTIES(VirtIOPCIProxy, nic),
> > > - DEFINE_PROP_UINT32("txtimer", VirtIOPCIProxy, txtimer, 1),
> > > + DEFINE_PROP_UINT32("txtimer", VirtIOPCIProxy, txtimer,
> > > + TXTIMER_DEFAULT),
> > > DEFINE_PROP_INT32("txburst", VirtIOPCIProxy, txburst, 256),
> > > DEFINE_PROP_END_OF_LIST(),
> > > },
> > > diff --git a/hw/virtio.h b/hw/virtio.h
> > > index 4051889..a1a17a2 100644
> > > --- a/hw/virtio.h
> > > +++ b/hw/virtio.h
> > > @@ -183,6 +183,12 @@ void virtio_update_irq(VirtIODevice *vdev);
> > > void virtio_bind_device(VirtIODevice *vdev, const VirtIOBindings *binding,
> > > void *opaque);
> > >
> > > +#ifdef CONFIG_IOTHREAD
> > > + #define TXTIMER_DEFAULT 0
> > > +#else
> > > + #define TXTIMER_DEFAULT 1
> > > +#endif
> > > +
> >
> > Add a comment explaning that this is just a performance optimization?
> >
> > > /* Base devices. */
> > > VirtIODevice *virtio_blk_init(DeviceState *dev, BlockConf *conf);
> > > VirtIODevice *virtio_net_init(DeviceState *dev, NICConf *conf,
> > >
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: jes.sorensen@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH 5/5] virtio-net: Switch default to new bottom half TX handler for iothread
Date: Wed, 1 Sep 2010 11:47:00 +0300 [thread overview]
Message-ID: <20100901084700.GA6136@redhat.com> (raw)
In-Reply-To: <1283293974.5826.154.camel@x201>
On Tue, Aug 31, 2010 at 04:32:54PM -0600, Alex Williamson wrote:
> On Tue, 2010-08-31 at 23:25 +0300, Michael S. Tsirkin wrote:
> > On Fri, Aug 27, 2010 at 04:37:45PM -0600, Alex Williamson wrote:
> > > The bottom half handler shows big improvements over the timer
> > > with few downsides, default to it when the iothread is enabled.
> > >
> > > Using the following tests, with the guest and host connected
> > > via tap+bridge:
> > >
> > > guest> netperf -t TCP_STREAM -H $HOST
> > > host> netperf -t TCP_STREAM -H $GUEST
> > > guest> netperf -t UDP_STREAM -H $HOST
> > > host> netperf -t UDP_STREAM -H $GUEST
> > > guest> netperf -t TCP_RR -H $HOST
> > >
> > > Results: base throughput, exits/throughput ->
> > > patched throughput, exits/throughput
> > >
> > > --enable-io-thread
> > > TCP guest->host 2737.77, 47.82 -> 6767.09, 29.15 = 247%, 61%
> > > TCP host->guest 2231.33, 74.00 -> 4125.80, 67.61 = 185%, 91%
> > > UDP guest->host 6281.68, 14.66 -> 12569.27, 1.98 = 200%, 14%
> > > UDP host->guest 275.91, 289.22 -> 264.80, 293.53 = 96%, 101%
> > > interations/s 1949.65, 82.97 -> 7417.56, 84.31 = 380%, 102%
> > >
> > > No --enable-io-thread
> > > TCP guest->host 3041.57, 55.11 -> 1038.93, 517.57 = 34%, 939%
> > > TCP host->guest 2416.03, 76.67 -> 5655.92, 55.52 = 234%, 72%
> > > UDP guest->host 12255.82, 6.11 -> 7775.87, 31.32 = 63%, 513%
> > > UDP host->guest 587.92, 245.95 -> 611.88, 239.92 = 104%, 98%
> > > interations/s 1975.59, 83.21 -> 8935.50, 88.18 = 452%, 106%
> > >
> > > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> >
> > parameter having different settings based on config
> > options might surprise some users. I don't think
> > we really need a parameter here ...
>
> I'm not a bit fan of this either, but I'd also prefer not to introduce a
> regression for a performance difference we know about in advance.
I agree. The comment was mainly about a parameter. If we make it a hidden
parameter (mainbe with x- prefix), this won't be an issue.
> It gets even more complicated when we factor in qemu-kvm, as it doesn't
> build with iothread enabled, but seems to get and even better boost in
> performance across the board thanks largely to the kvm-irqchip. Should
> we instead make this a configure option? --enable-virtio-net-txbh?
That'll work too.
> Thanks,
>
> Alex
>
> > > ---
> > >
> > > hw/s390-virtio-bus.c | 3 ++-
> > > hw/syborg_virtio.c | 3 ++-
> > > hw/virtio-pci.c | 3 ++-
> > > hw/virtio.h | 6 ++++++
> > > 4 files changed, 12 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/hw/s390-virtio-bus.c b/hw/s390-virtio-bus.c
> > > index 1483362..985f99a 100644
> > > --- a/hw/s390-virtio-bus.c
> > > +++ b/hw/s390-virtio-bus.c
> > > @@ -328,7 +328,8 @@ static VirtIOS390DeviceInfo s390_virtio_net = {
> > > .qdev.size = sizeof(VirtIOS390Device),
> > > .qdev.props = (Property[]) {
> > > DEFINE_NIC_PROPERTIES(VirtIOS390Device, nic),
> > > - DEFINE_PROP_UINT32("txtimer", VirtIOS390Device, txtimer, 1),
> > > + DEFINE_PROP_UINT32("txtimer", VirtIOS390Device, txtimer,
> > > + TXTIMER_DEFAULT),
> > > DEFINE_PROP_INT32("txburst", VirtIOS390Device, txburst, 256),
> > > DEFINE_PROP_END_OF_LIST(),
> > > },
> > > diff --git a/hw/syborg_virtio.c b/hw/syborg_virtio.c
> > > index 7b76972..ee5746d 100644
> > > --- a/hw/syborg_virtio.c
> > > +++ b/hw/syborg_virtio.c
> > > @@ -300,7 +300,8 @@ static SysBusDeviceInfo syborg_virtio_net_info = {
> > > .qdev.props = (Property[]) {
> > > DEFINE_NIC_PROPERTIES(SyborgVirtIOProxy, nic),
> > > DEFINE_VIRTIO_NET_FEATURES(SyborgVirtIOProxy, host_features),
> > > - DEFINE_PROP_UINT32("txtimer", SyborgVirtIOProxy, txtimer, 1),
> > > + DEFINE_PROP_UINT32("txtimer", SyborgVirtIOProxy, txtimer,
> > > + TXTIMER_DEFAULT),
> > > DEFINE_PROP_INT32("txburst", SyborgVirtIOProxy, txburst, 256),
> > > DEFINE_PROP_END_OF_LIST(),
> > > }
> > > diff --git a/hw/virtio-pci.c b/hw/virtio-pci.c
> > > index e025c09..9740f57 100644
> > > --- a/hw/virtio-pci.c
> > > +++ b/hw/virtio-pci.c
> > > @@ -695,7 +695,8 @@ static PCIDeviceInfo virtio_info[] = {
> > > DEFINE_PROP_UINT32("vectors", VirtIOPCIProxy, nvectors, 3),
> > > DEFINE_VIRTIO_NET_FEATURES(VirtIOPCIProxy, host_features),
> > > DEFINE_NIC_PROPERTIES(VirtIOPCIProxy, nic),
> > > - DEFINE_PROP_UINT32("txtimer", VirtIOPCIProxy, txtimer, 1),
> > > + DEFINE_PROP_UINT32("txtimer", VirtIOPCIProxy, txtimer,
> > > + TXTIMER_DEFAULT),
> > > DEFINE_PROP_INT32("txburst", VirtIOPCIProxy, txburst, 256),
> > > DEFINE_PROP_END_OF_LIST(),
> > > },
> > > diff --git a/hw/virtio.h b/hw/virtio.h
> > > index 4051889..a1a17a2 100644
> > > --- a/hw/virtio.h
> > > +++ b/hw/virtio.h
> > > @@ -183,6 +183,12 @@ void virtio_update_irq(VirtIODevice *vdev);
> > > void virtio_bind_device(VirtIODevice *vdev, const VirtIOBindings *binding,
> > > void *opaque);
> > >
> > > +#ifdef CONFIG_IOTHREAD
> > > + #define TXTIMER_DEFAULT 0
> > > +#else
> > > + #define TXTIMER_DEFAULT 1
> > > +#endif
> > > +
> >
> > Add a comment explaning that this is just a performance optimization?
> >
> > > /* Base devices. */
> > > VirtIODevice *virtio_blk_init(DeviceState *dev, BlockConf *conf);
> > > VirtIODevice *virtio_net_init(DeviceState *dev, NICConf *conf,
> > >
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2010-09-01 8:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 22:36 [PATCH 0/5] virtio-net: More configurability and bh handling for tx Alex Williamson
2010-08-27 22:36 ` [Qemu-devel] " Alex Williamson
2010-08-27 22:37 ` [PATCH 1/5] virtio-net: Make tx_timer timeout configurable Alex Williamson
2010-08-27 22:37 ` [Qemu-devel] " Alex Williamson
2010-08-31 18:00 ` Chris Wright
2010-08-31 18:00 ` [Qemu-devel] " Chris Wright
2010-08-31 18:07 ` Alex Williamson
2010-08-31 18:07 ` Alex Williamson
2010-08-31 19:29 ` Chris Wright
2010-08-27 22:37 ` [PATCH 2/5] virtio-net: Limit number of packets sent per TX flush Alex Williamson
2010-08-27 22:37 ` [Qemu-devel] " Alex Williamson
2010-08-31 20:23 ` Michael S. Tsirkin
2010-08-31 20:23 ` [Qemu-devel] " Michael S. Tsirkin
2010-08-27 22:37 ` [PATCH 3/5] virtio-net: Rename tx_timer_active to tx_waiting Alex Williamson
2010-08-27 22:37 ` [Qemu-devel] " Alex Williamson
2010-08-27 22:37 ` [PATCH 4/5] virtio-net: Introduce a new bottom half packet TX Alex Williamson
2010-08-27 22:37 ` [Qemu-devel] " Alex Williamson
2010-08-31 20:14 ` Michael S. Tsirkin
2010-08-31 20:14 ` [Qemu-devel] " Michael S. Tsirkin
2010-08-31 20:33 ` Alex Williamson
2010-08-31 20:33 ` [Qemu-devel] " Alex Williamson
2010-09-01 9:47 ` Michael S. Tsirkin
2010-09-01 9:47 ` [Qemu-devel] " Michael S. Tsirkin
2010-08-27 22:37 ` [PATCH 5/5] virtio-net: Switch default to new bottom half TX handler for iothread Alex Williamson
2010-08-27 22:37 ` [Qemu-devel] " Alex Williamson
2010-08-31 20:25 ` Michael S. Tsirkin
2010-08-31 20:25 ` [Qemu-devel] " Michael S. Tsirkin
2010-08-31 22:32 ` Alex Williamson
2010-08-31 22:32 ` [Qemu-devel] " Alex Williamson
2010-08-31 22:46 ` Anthony Liguori
2010-08-31 22:46 ` [Qemu-devel] " Anthony Liguori
2010-09-01 6:21 ` Stefan Hajnoczi
2010-09-01 6:21 ` [Qemu-devel] " Stefan Hajnoczi
2010-09-01 8:47 ` Michael S. Tsirkin [this message]
2010-09-01 8:47 ` Michael S. Tsirkin
2010-08-31 20:20 ` [PATCH 0/5] virtio-net: More configurability and bh handling for tx Michael S. Tsirkin
2010-08-31 20:20 ` [Qemu-devel] " Michael S. Tsirkin
2010-08-31 20:27 ` Michael S. Tsirkin
2010-08-31 20:27 ` [Qemu-devel] " Michael S. Tsirkin
2010-08-31 21:33 ` Anthony Liguori
2010-08-31 21:33 ` [Qemu-devel] " Anthony Liguori
2010-08-31 22:26 ` Alex Williamson
2010-08-31 22:26 ` [Qemu-devel] " Alex Williamson
2010-09-01 10:40 ` Michael S. Tsirkin
2010-09-01 10:40 ` [Qemu-devel] " 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=20100901084700.GA6136@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jes.sorensen@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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.