From: Bruce Richardson <bruce.richardson@intel.com>
To: "Xie, Huawei" <huawei.xie@intel.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/3 v3] virtio: Tx performance improvements
Date: Wed, 16 Mar 2016 17:40:38 +0000 [thread overview]
Message-ID: <20160316174038.GA10308@bricha3-MOBL3> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B4C66E45C@SHSMSX101.ccr.corp.intel.com>
On Wed, Mar 16, 2016 at 08:25:08AM +0000, Xie, Huawei wrote:
> On 3/14/2016 6:56 PM, Richardson, Bruce wrote:
> > On Fri, Mar 04, 2016 at 10:19:18AM -0800, Stephen Hemminger wrote:
> >> This patch series uses virtio negotiated features to allow for
> >> more packets to be queued to host even though the default QEMU/KVM
> >> virtio queue is very small 256 elements.
> >>
> >> Stephen Hemminger (3):
> >> virtio: use indirect ring elements
> >> virtio: use any layout on transmit
> >> virtio: optimize transmit enqueue
> >>
> > These patches require an ack to merge. Virtio maintainers, can you please
> > review and ack if ok.
> >
> > /Bruce
> >
> Acked in the previous release window.
>
> Acked-by: Huawei Xie <huawei.xie@intel.com>
>
Pushed to dpdk-next-net/rel_16_04
/Bruce
prev parent reply other threads:[~2016-03-16 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 18:19 Stephen Hemminger
2016-03-04 18:19 ` [dpdk-dev] [PATCH 1/3] virtio: use indirect ring elements Stephen Hemminger
2016-03-04 18:19 ` [dpdk-dev] [PATCH 2/3] virtio: use any layout on transmit Stephen Hemminger
2016-03-04 18:19 ` [dpdk-dev] [PATCH 3/3] virtio: optimize transmit enqueue Stephen Hemminger
2016-03-14 10:56 ` [dpdk-dev] [PATCH 0/3 v3] virtio: Tx performance improvements Bruce Richardson
2016-03-14 12:24 ` Yuanhan Liu
2016-03-16 8:25 ` Xie, Huawei
2016-03-16 17:40 ` Bruce Richardson [this message]
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=20160316174038.GA10308@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.com \
--cc=stephen@networkplumber.org \
--cc=yuanhan.liu@linux.intel.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 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).