From: "Pai G, Sunil" <sunil.pai.g@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Van Haaren, Harry" <harry.van.haaren@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Hu, Jiayu" <jiayu.hu@intel.com>,
"Ferriter, Cian" <cian.ferriter@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
"Stokes, Ian" <ian.stokes@intel.com>,
"Xia, Chenbo" <chenbo.xia@intel.com>
Subject: Re: [dpdk-dev] [PATCH RFC 0/1] vhost-add-DMADEV-support-for-async-datapath
Date: Tue, 31 Aug 2021 13:03:37 +0000 [thread overview]
Message-ID: <BYAPR11MB38145974B0923149056A740CBDCC9@BYAPR11MB3814.namprd11.prod.outlook.com> (raw)
In-Reply-To: <6cd84154-cf2d-593c-b9c4-9df14d18558f@redhat.com>
Hi Maxime,
<snip>
> 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?
>
I did some quick changes for the vhost sample app but only for the Northbound path.
https://patches.dpdk.org/project/dpdk/patch/20210831125924.3353952-1-sunil.pai.g@intel.com/
Please note that the patch is untested.
<snip>
next prev parent reply other threads:[~2021-08-31 13:04 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 ` [dpdk-dev] [PATCH RFC 0/1] vhost-add-DMADEV-support-for-async-datapath Maxime Coquelin
2021-08-31 13:03 ` Pai G, Sunil [this message]
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=BYAPR11MB38145974B0923149056A740CBDCC9@BYAPR11MB3814.namprd11.prod.outlook.com \
--to=sunil.pai.g@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chenbo.xia@intel.com \
--cc=cian.ferriter@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=ian.stokes@intel.com \
--cc=jiayu.hu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=qian.q.xu@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).