From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Wenwu Ma <wenwux.ma@intel.com>, chenbo.xia@intel.com, dev@dpdk.org
Cc: jiayu.hu@intel.com, yinan.wang@intel.com, xingguang.he@intel.com,
weix.ling@intel.com
Subject: Re: [PATCH] vhost: support sync copy when data buffer is small
Date: Tue, 19 Apr 2022 11:10:27 +0200 [thread overview]
Message-ID: <a9e33c52-12c7-75be-f8ea-c82f0c9cbfc9@redhat.com> (raw)
In-Reply-To: <20220411133836.200783-1-wenwux.ma@intel.com>
Hi Wenwu,
On 4/11/22 15:38, Wenwu Ma wrote:
> In async datapath, if the length of data buffer
> is less than 256, the data will be copied by CPU
> instead of DMA.
>
> Signed-off-by: Wenwu Ma <wenwux.ma@intel.com>
> ---
> lib/vhost/vhost.h | 6 ++-
> lib/vhost/virtio_net.c | 96 ++++++++++++++++++++++++++++++------------
> 2 files changed, 73 insertions(+), 29 deletions(-)
>
As I mentioned in the past, let's have a DMA-only solution working
before trying to support CPU copy for small packets.
Thanks,
Maxime
next prev parent reply other threads:[~2022-04-19 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 13:38 Wenwu Ma
2022-04-19 9:10 ` Maxime Coquelin [this message]
2022-05-23 0:38 ` Hu, Jiayu
2022-05-23 8:49 ` 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=a9e33c52-12c7-75be-f8ea-c82f0c9cbfc9@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=weix.ling@intel.com \
--cc=wenwux.ma@intel.com \
--cc=xingguang.he@intel.com \
--cc=yinan.wang@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).