DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Jiayu Hu <jiayu.hu@intel.com>, dev@dpdk.org
Cc: chenbo.xia@intel.com, david.marchand@redhat.com,
	Cheng Jiang <cheng1.jiang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] vhost: remove copy threshold for async vhost
Date: Fri, 27 Aug 2021 10:20:52 +0200	[thread overview]
Message-ID: <28803bbb-9a2d-0694-903e-cdc8fafedcbf@redhat.com> (raw)
In-Reply-To: <1629463466-450012-1-git-send-email-jiayu.hu@intel.com>

Hi Jiayu,

Thanks for working on it!

On 8/20/21 2:44 PM, Jiayu Hu wrote:
> Copy threshold is introduced in async vhost data path to select
> the appropriate copy engine to do copies for higher efficiency.
> However, it may cause packets out-of-order, and it also causes
> data path performance unpredictable.
> 
> Therefore, this patch removes copy threshold support in async vhost
> data path.
> 
> Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
> Signed-off-by: Cheng Jiang <cheng1.jiang@intel.com>
> ---
>  doc/guides/prog_guide/vhost_lib.rst |   7 -
>  examples/vhost/main.c               |  22 +-
>  lib/vhost/rte_vhost_async.h         |  22 +-
>  lib/vhost/vhost.c                   |   6 +-
>  lib/vhost/vhost.h                   |   1 -
>  lib/vhost/virtio_net.c              | 439 +++++++++---------------------------
>  6 files changed, 116 insertions(+), 381 deletions(-)
> 

It looks good to me, and simplifies the code a lot.

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime


  reply	other threads:[~2021-08-27  8:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 12:44 Jiayu Hu
2021-08-27  8:20 ` Maxime Coquelin [this message]
2021-09-14 11:24 ` Maxime Coquelin
2021-09-16 11:15 ` Ferruh Yigit
2021-09-16 11:34   ` Maxime Coquelin
2021-09-16 11:55     ` Xia, Chenbo

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=28803bbb-9a2d-0694-903e-cdc8fafedcbf@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=cheng1.jiang@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jiayu.hu@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).