From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: dev@dpdk.org
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] vhost: avoid memory write on net header when necessary
Date: Wed, 19 Apr 2017 14:11:27 +0800 [thread overview]
Message-ID: <20170419061127.GB31523@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1492156398-14405-1-git-send-email-yuanhan.liu@linux.intel.com>
On Fri, Apr 14, 2017 at 03:53:18PM +0800, Yuanhan Liu wrote:
> Like what we did for virtio PMD driver [0][1], we could also apply such
> trick to vhost, to avoid the memory write on net header when necessary.
>
> [0]: c9ea670c1dc7 ("net/virtio: fix performance regression due to TSO")
> [1]: 16994abee215 ("net/virtio: optimize header reset on any layout")
>
> With this, the cache issue of the mergeable path is again greatly reduced:
> even the write of "num_buffers" could be avoided. A quick PVP test shows
> the gap between the mergeable Rx and non-mergable Rx is pretty small now:
> they are basically the same in my test.
>
> Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Applied to dpdk-next-virtio.
--yliu
prev parent reply other threads:[~2017-04-19 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 7:53 Yuanhan Liu
2017-04-19 6:11 ` Yuanhan Liu [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=20170419061127.GB31523@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@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 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).