DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Sunil Pai G <sunil.pai.g@intel.com>, dev@dpdk.org
Cc: harry.van.haaren@intel.com, bruce.richardson@intel.com,
	Jiayu.Hu@intel.com, Cian.Ferriter@intel.com,
	john.mcnamara@intel.com, qian.q.xu@intel.com,
	ian.stokes@intel.com, Chenbo Xia <chenbo.xia@intel.com>
Subject: Re: [dpdk-dev] [PATCH RFC 0/1] vhost-add-DMADEV-support-for-async-datapath
Date: Mon, 30 Aug 2021 16:35:18 +0200	[thread overview]
Message-ID: <6cd84154-cf2d-593c-b9c4-9df14d18558f@redhat.com> (raw)
In-Reply-To: <20210823095355.2478423-1-sunil.pai.g@intel.com>

Hi Sunil,

On 8/23/21 11:53 AM, Sunil Pai G wrote:
> Note to the reader:
> -------------------
> The intent of this patch is to explore possible different approaches
> of async implementations.
> Please consider this patch for discussions only and not for
> merge/upstream.

Thanks for sharing, that will indeed help to find the best solution.
I'm just wondering if you have the vhost example part of this rework, so
that we can understand what are the impacts on app side?

> This patch simplifies the vhost async datapath usability by
> utilizing the generic DMADEV API's to perform packet copy.
> 
> Previously, it was required by the application to implement its
> own DMA enabling logic making it difficult to adopt this feature.
> Having a common implementation in vhost library allows
> for easier adoption.
> 
> The usability of async datapath is enhanced by extending the
> API's to include a DMADEV ID to be passed by the application.
> This provides flexibility to applications to decide which DMADEV to be used.
> 
> 
> Sunil Pai G (1):
>   vhost: Add DMADEV support for async datapath.
> 
>  lib/vhost/meson.build       |   2 +-
>  lib/vhost/rte_vhost_async.h |  55 +------
>  lib/vhost/vhost.c           |  46 +++---
>  lib/vhost/vhost.h           |  24 ++-
>  lib/vhost/virtio_net.c      | 311 +++++++++++++++++++++++++++++++-----
>  5 files changed, 316 insertions(+), 122 deletions(-)
> 


  parent reply	other threads:[~2021-08-30 14:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23  9:53 Sunil Pai G
2021-08-23  9:53 ` [dpdk-dev] [PATCH RFC 1/1] vhost: add DMADEV support for async datapath Sunil Pai G
2021-08-30 14:35 ` Maxime Coquelin [this message]
2021-08-31 13:03   ` [dpdk-dev] [PATCH RFC 0/1] vhost-add-DMADEV-support-for-async-datapath Pai G, Sunil
2021-09-13  9:48     ` Pai G, Sunil

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=6cd84154-cf2d-593c-b9c4-9df14d18558f@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=Cian.Ferriter@intel.com \
    --cc=Jiayu.Hu@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.com \
    --cc=ian.stokes@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=sunil.pai.g@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).