From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Jerin Jacob <jerinjacobk@gmail.com>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Ferruh Yigit" <ferruh.yigit@intel.com>,
"Ajit Khaparde (ajit.khaparde@broadcom.com)"
<ajit.khaparde@broadcom.com>, "Andrew Boyer" <aboyer@pensando.io>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
"Beilei Xing" <beilei.xing@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Chas Williams" <chas3@att.com>,
"Xia, Chenbo" <chenbo.xia@intel.com>,
"Ciara Loftus" <ciara.loftus@intel.com>,
"Devendra Singh Rawat" <dsinghrawat@marvell.com>,
"Ed Czeck" <ed.czeck@atomicrules.com>,
"Evgeny Schemeilin" <evgenys@amazon.com>,
"Gaetan Rivet" <grive@u256.net>,
"Gagandeep Singh" <g.singh@nxp.com>,
"Guoyang Zhou" <zhouguoyang@huawei.com>,
"Haiyue Wang" <haiyue.wang@intel.com>,
"Harman Kalra" <hkalra@marvell.com>,
"heinrich.kuhn@corigine.com" <heinrich.kuhn@corigine.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Hyong Youb Kim" <hyonkim@cisco.com>,
"Igor Chauskin" <igorch@amazon.com>,
"Igor Russkikh" <irusskikh@marvell.com>,
"Jakub Grajciar" <jgrajcia@cisco.com>,
"Jasvinder Singh" <jasvinder.singh@intel.com>,
"Jian Wang" <jianwang@trustnetic.com>,
"Jiawen Wu" <jiawenwu@trustnetic.com>,
"Jingjing Wu" <jingjing.wu@intel.com>,
"John Daley" <johndale@cisco.com>,
"John Miller" <john.miller@atomicrules.com>,
"John W. Linville" <linville@tuxdriver.com>,
"Wiles, Keith" <keith.wiles@intel.com>,
"Kiran Kumar K" <kirankumark@marvell.com>,
"Lijun Ou" <oulijun@huawei.com>,
"Liron Himi" <lironh@marvell.com>,
"Long Li" <longli@microsoft.com>,
"Marcin Wojtas" <mw@semihalf.com>,
"Martin Spinler" <spinler@cesnet.cz>,
"Matan Azrad" <matan@nvidia.com>,
"Matt Peters" <matt.peters@windriver.com>,
"Maxime Coquelin" <maxime.coquelin@redhat.com>,
"Michal Krawczyk" <mk@semihalf.com>,
"Min Hu (Connor" <humin29@huawei.com>,
"Pradeep Kumar Nalla" <pnalla@marvell.com>,
"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
"Qiming Yang" <qiming.yang@intel.com>,
"Qi Zhang" <qi.z.zhang@intel.com>,
"Radha Mohan Chintakuntla" <radhac@marvell.com>,
"Rahul Lakkireddy" <rahul.lakkireddy@chelsio.com>,
"Rasesh Mody" <rmody@marvell.com>,
"Rosen Xu" <rosen.xu@intel.com>,
"Sachin Saxena" <sachin.saxena@oss.nxp.com>,
"Satha Koteswara Rao Kottidi" <skoteshwar@marvell.com>,
"Shahed Shaikh" <shshaikh@marvell.com>,
"Shai Brandes" <shaibran@amazon.com>,
"Shepard Siegel" <shepard.siegel@atomicrules.com>,
"Somalapuram Amaranath" <asomalap@amd.com>,
"Somnath Kotur" <somnath.kotur@broadcom.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
"Steven Webster" <steven.webster@windriver.com>,
"Sunil Kumar Kori" <skori@marvell.com>,
"Tetsuya Mukawa" <mtetsuyah@gmail.com>,
"Veerasenareddy Burru" <vburru@marvell.com>,
"Viacheslav Ovsiienko" <viacheslavo@nvidia.com>,
"Xiao Wang" <xiao.w.wang@intel.com>,
"Xiaoyun Wang" <cloud.wangxiaoyun@huawei.com>,
"Yisen Zhuang" <yisen.zhuang@huawei.com>,
"Yong Wang" <yongwang@vmware.com>,
"Ziyang Xuan" <xuanziyang2@huawei.com>,
"Prasun Kapoor" <pkapoor@marvell.com>,
"nadavh@marvell.com" <nadavh@marvell.com>,
"Satananda Burla" <sburla@marvell.com>,
"Narayana Prasad" <pathreya@marvell.com>,
"Akhil Goyal" <gakhil@marvell.com>,
"Ray Kinsella" <mdr@ashroe.eu>,
"Dmitry Kozlyuk" <dmitry.kozliuk@gmail.com>,
"Anatoly Burakov" <anatoly.burakov@intel.com>,
"Cristian Dumitrescu" <cristian.dumitrescu@intel.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Ruifeng Wang" <Ruifeng.Wang@arm.com>,
"David Christensen" <drc@linux.vnet.ibm.com>,
"Olivier Matz" <olivier.matz@6wind.com>,
"Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>,
"Ashwin Sekhar Thalakalath Kottilveetil" <asekhar@marvell.com>,
"Pavan Nikhilesh" <pbhagavatula@marvell.com>,
"Elena Agostini" <eagostini@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"techboard@dpdk.org" <techboard@dpdk.org>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: RE: [dpdk-dev] Minutes of Technical Board Meeting, 2021-Oct-27
Date: Thu, 18 Nov 2021 15:13:39 +0000 [thread overview]
Message-ID: <DBAPR08MB5814CE829282BC0011DD70AC989B9@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1NhOKdZHFAHDDNyMFSoJ4g2Lqaypa0Vv5vc_u-jVCZ0vQ@mail.gmail.com>
<snip>
> > > There was a comment to remove the TLV length. I will do that next
> > > version with implementation.
> > >
> > > Identified the following set of work for this.
> > >
> > > 1) Common code at lib/dwa/
> > > 2) Marvell DPU based driver at drivers/dwa/cnxk/
> > > 3) Test application at app/test-dwa/
> > > 4) It is possible to have an SW driver(To allow non-specialized HW
> > > to use the
> > > framework) for this by:
> > > a) Emulate DWA HW as a separate DPDK process
> > > b) Add drivers/dwa/sw/ and use memif driver so to create a
> > > communication channel between emulated DWA HW process and DPDK
> application.
> > Why use memif driver? Why not ring-pmd?
>
> Planning to emulation DWA accelerator functional model as a separate DPDK
> process in SW case.
You mean the primary and secondary processes correct?
> Therefore memif is the ideal choice as it supports zero-copy of the data as
> well.
> https://doc.dpdk.org/guides/nics/memif.html
Zero-copy in memif is nothing but exchanging pointers to shared data.
The rings work across the primary and secondary processes and are always zero-copy.
We are doing some perf comparisons between memif and rings, will let you know once we have the data.
>
> >
> > > c) Add drivers/dwa/sw/profiles//l3fwd - To implement l3fwd profile
> > > using DPDK libraries for SW driver.
> > >
> > > I think, Item (4) aka SW drivers as useful(We don't need to
> > > implement for all profiles, I think, just for l3fwd it make sense
> > > to add, to allow to use of the framework in just SW mode).
> > > Is there any opinion on adding item (4) in DPDK? I saw mixed
> > > opinions earlier on this. I would like to understand, Is there any
> > > objection to doing
> > > item(4) in DPDK as it needs a good amount of work and I don't want
> > > to do throw it away if the community doesn't like this.
> > > Any opinion?
> > >
> > > [1]
> > > http://mails.dpdk.org/archives/dev/2021-October/226070.html
> > >
> > <snip>
next prev parent reply other threads:[~2021-11-18 15:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 15:39 Ananyev, Konstantin
2021-11-11 11:44 ` Jerin Jacob
2021-11-11 12:32 ` Ananyev, Konstantin
2021-11-12 0:56 ` Honnappa Nagarahalli
2021-11-12 1:46 ` Ananyev, Konstantin
2021-11-12 6:19 ` Jerin Jacob
2021-11-12 2:24 ` Honnappa Nagarahalli
2021-11-12 6:26 ` Jerin Jacob
2021-11-18 15:13 ` Honnappa Nagarahalli [this message]
2021-11-18 16:27 ` Jerin Jacob
2021-11-18 20:07 ` Honnappa Nagarahalli
2021-11-19 4:34 ` Jerin Jacob
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=DBAPR08MB5814CE829282BC0011DD70AC989B9@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=aboyer@pensando.io \
--cc=ajit.khaparde@broadcom.com \
--cc=anatoly.burakov@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=asekhar@marvell.com \
--cc=asomalap@amd.com \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chas3@att.com \
--cc=chenbo.xia@intel.com \
--cc=ciara.loftus@intel.com \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=drc@linux.vnet.ibm.com \
--cc=dsinghrawat@marvell.com \
--cc=eagostini@nvidia.com \
--cc=ed.czeck@atomicrules.com \
--cc=evgenys@amazon.com \
--cc=ferruh.yigit@intel.com \
--cc=g.singh@nxp.com \
--cc=gakhil@marvell.com \
--cc=grive@u256.net \
--cc=haiyue.wang@intel.com \
--cc=heinrich.kuhn@corigine.com \
--cc=hemant.agrawal@nxp.com \
--cc=hkalra@marvell.com \
--cc=humin29@huawei.com \
--cc=hyonkim@cisco.com \
--cc=igorch@amazon.com \
--cc=irusskikh@marvell.com \
--cc=jasvinder.singh@intel.com \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinjacobk@gmail.com \
--cc=jgrajcia@cisco.com \
--cc=jianwang@trustnetic.com \
--cc=jiawenwu@trustnetic.com \
--cc=jingjing.wu@intel.com \
--cc=john.miller@atomicrules.com \
--cc=johndale@cisco.com \
--cc=keith.wiles@intel.com \
--cc=kirankumark@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=linville@tuxdriver.com \
--cc=lironh@marvell.com \
--cc=longli@microsoft.com \
--cc=matan@nvidia.com \
--cc=matt.peters@windriver.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=maxime.coquelin@redhat.com \
--cc=mdr@ashroe.eu \
--cc=mk@semihalf.com \
--cc=mtetsuyah@gmail.com \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=nd@arm.com \
--cc=ndabilpuram@marvell.com \
--cc=olivier.matz@6wind.com \
--cc=oulijun@huawei.com \
--cc=pathreya@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=pkapoor@marvell.com \
--cc=pnalla@marvell.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=radhac@marvell.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=rmody@marvell.com \
--cc=rosen.xu@intel.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=sburla@marvell.com \
--cc=shaibran@amazon.com \
--cc=shepard.siegel@atomicrules.com \
--cc=shshaikh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=somnath.kotur@broadcom.com \
--cc=spinler@cesnet.cz \
--cc=steven.webster@windriver.com \
--cc=sthemmin@microsoft.com \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
--cc=vburru@marvell.com \
--cc=viacheslavo@nvidia.com \
--cc=xiao.w.wang@intel.com \
--cc=xuanziyang2@huawei.com \
--cc=yisen.zhuang@huawei.com \
--cc=yongwang@vmware.com \
--cc=zhouguoyang@huawei.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).