From: Ian Campbell <Ian.Campbell@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, <netdev@vger.kernel.org>,
<xen-devel@lists.xenproject.org>,
Jonathan Davies <jonathan.davies@citrix.com>
Subject: Re: [Xen-devel] [RFC PATCHv1 net-next] xen-netback: always fully coalesce guest Rx packets
Date: Tue, 20 Jan 2015 11:23:13 +0000 [thread overview]
Message-ID: <1421752993.10440.225.camel@citrix.com> (raw)
In-Reply-To: <54BD408A.6080405@citrix.com>
On Mon, 2015-01-19 at 17:36 +0000, David Vrabel wrote:
> On 13/01/15 14:30, Wei Liu wrote:
> > On Tue, Jan 13, 2015 at 02:05:17PM +0000, David Vrabel wrote:
> >> Always fully coalesce guest Rx packets into the minimum number of ring
> >> slots. Reducing the number of slots per packet has significant
> >> performance benefits (e.g., 7.2 Gbit/s to 11 Gbit/s in an off-host
> >> receive test).
> >>
> >
> > Good number.
> >
> >> However, this does increase the number of grant ops per packet which
> >> decreases performance with some workloads (intrahost VM to VM)
> >
> > Do you have figures before and after this change?
>
> Some better (more rigorous) results done by Jonathan Davies shows no
> regressions with full coalescing even without the grant copy
> optimization, and a big improvement to single stream receive.
>
> baseline Full coalesce
> Interhost aggregate 24 Gb/s 24 Gb/s
> Interhost VM receive 7.2 Gb/s 11 Gb/s
> Intrahost single stream 14 Gb/s 14 Gb/s
> Intrahost aggregate 34 Gb/s 34 Gb/s
Do you have a third column to hand, for Full-coalesce w/ grant copy
optimisation case? (Don't worry if not)
Ian.
next prev parent reply other threads:[~2015-01-20 11:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 14:05 [RFC PATCHv1 net-next] xen-netback: always fully coalesce guest Rx packets David Vrabel
2015-01-13 14:30 ` Wei Liu
2015-01-19 17:36 ` [Xen-devel] " David Vrabel
2015-01-20 11:21 ` Ian Campbell
2015-01-20 11:21 ` [Xen-devel] " Ian Campbell
2015-01-20 11:23 ` Ian Campbell [this message]
2015-01-20 11:23 ` Ian Campbell
2015-01-19 17:36 ` David Vrabel
2015-01-13 14:30 ` Wei Liu
2015-01-20 11:34 ` Ian Campbell
2015-01-20 11:34 ` Ian Campbell
2015-01-20 11:38 ` David Vrabel
2015-01-20 11:38 ` David Vrabel
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=1421752993.10440.225.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=jonathan.davies@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.