From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: junjie.j.chen@intel.com, jianfeng.tan@intel.com,
john.mcnamara@intel.com, marko.kovacevic@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] doc/vhost: update zero copy perfromance tip
Date: Fri, 4 May 2018 14:49:25 +0200 [thread overview]
Message-ID: <780e9e32-b772-0828-dd14-42159ccc6c89@redhat.com> (raw)
In-Reply-To: <1524730400-252654-1-git-send-email-junjie.j.chen@intel.com>
On 04/26/2018 10:13 AM, junjie.j.chen@intel.com wrote:
> In VM2NIC case zero copy may need some tuning to get best performance. This
> patch describes the zero copy starved case and provides a tuning tip.
>
> Signed-off-by: Junjie Chen <junjie.j.chen@intel.com>
> ---
> doc/guides/prog_guide/vhost_lib.rst | 20 ++++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2018-05-04 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 8:13 [dpdk-dev] [PATCH] " Junjie Chen
2018-05-04 12:49 ` Maxime Coquelin [this message]
2018-05-04 15:12 ` Maxime Coquelin
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=780e9e32-b772-0828-dd14-42159ccc6c89@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=john.mcnamara@intel.com \
--cc=junjie.j.chen@intel.com \
--cc=marko.kovacevic@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).