From: Jerin Jacob <jerinjacobk@gmail.com>
To: Tom Herbert <tom@herbertland.com>
Cc: "Thomas Monjalon" <thomas@monjalon.net>,
"Jerin Jacob" <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
"Ferruh Yigit" <ferruh.yigit@intel.com>,
"Ajit Khaparde" <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,
"Hemant Agrawal" <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, "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>,
"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>,
"David Christensen" <drc@linux.vnet.ibm.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.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>,
"David Marchand" <david.marchand@redhat.com>,
felipe@sipanda.io, chethan@sipanda.io, siva@sipanda.io,
"Tom Herbert" <tom@sipanda.io>
Subject: Re: [dpdk-dev] [RFC PATCH 0/1] Dataplane Workload Accelerator library
Date: Wed, 20 Oct 2021 11:08:17 +0530 [thread overview]
Message-ID: <CALBAE1N-109WrGnYtB1_JRrMq-1sbchNvTw8O1T60KfobjWQyQ@mail.gmail.com> (raw)
In-Reply-To: <CALx6S35ZUy0yRhhWVCz8EHHQSaCT5tKXghVj7HQ5uu-w71PfaQ@mail.gmail.com>
On Wed, Oct 20, 2021 at 2:12 AM Tom Herbert <tom@herbertland.com> wrote:
>
> On Tue, Oct 19, 2021 at 12:36 PM Jerin Jacob <jerinjacobk@gmail.com> wrote:
> >
> > On Wed, Oct 20, 2021 at 12:38 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> > >
> > > 19/10/2021 20:14, jerinj@marvell.com:
> > > > Definition of Dataplane Workload Accelerator
> > > > --------------------------------------------
> > > > Dataplane Workload Accelerator(DWA) typically contains a set of CPUs,
> > > > Network controllers and programmable data acceleration engines for
> > > > packet processing, cryptography, regex engines, baseband processing, etc.
> > > > This allows DWA to offload compute/packet processing/baseband/
> > > > cryptography-related workload from the host CPU to save the cost and power.
> > > > Also to enable scaling the workload by adding DWAs to the Host CPU as needed.
> > > >
> > > > Unlike other devices in DPDK, the DWA device is not fixed-function
> > > > due to the fact that it has CPUs and programmable HW accelerators.
> > > > This enables DWA personality/workload to be completely programmable.
> > > > Typical examples of DWA offloads are Flow/Session management,
> > > > Virtual switch, TLS offload, IPsec offload, l3fwd offload, etc.
> > >
> > > If I understand well, the idea is to abstract the offload
> > > of some stack layers in the hardware.
> >
> > Yes. It may not just HW, For expressing the complicated workloads
> > may need CPU and/or other HW accelerators.
> >
> > > I am not sure we should give an API for such stack layers in DPDK.
> >
> > Why not?
> >
> > > It looks to be the role of the dataplane application to finely manage
> > > how to use the hardware for a specific dataplane.
> >
> > It is possible with this scheme.
> >
> > > I believe the API for such layer would be either too big, or too limited,
> > > or not optimized for specific needs.
> >
> > It will be optimized for specific needs as applications ask for what to do?
> > not how to do?
> >
> > > If we really want to automate or abstract the HW/SW co-design,
> > > I think we should better look at compiler work like P4 or PANDA.
> >
> > The compiler stuff is very static in nature. It can address the packet
> > transformation
> > workloads. Not the ones like IPsec or baseband offload.
> > Another way to look at it, GPU RFC started just because you are not able
> > to express all the workload in P4.
>
> Hi,
>
> Indeed, you may want to look at PANDA
> (https://github.com/panda-net/panda) for this purpose especially with
> regard to HW/SW co-design. Fundamentally, it is C/C++ so it's "Turing
> Complete" as far as being able to express arbitrary workloads. The
> program structure abstracts out any underlying details of the runtime
> environment (hence it is "right once, run anywhere"). It is the
> auspices of a compiler to convert the user's expression of intent into
> optimized code for the backend; the backends can be software, such as
> DPDK (which PANDA will soon support), or even hardware. In any case,
> the code emitted will be optimized per the environment, taking
> advantage of hardware acceleration for instance, which leads to the
> PANDA mantra "write once, run anywhere, run well". This does require
> APIs to control hardware acceleration, but our goal is to hide that
> complexity from the user without the loss of benefits of emerging
> hardware features. Also with emerging compiler techniques like LLVM's
> MLIR and dynamically defined instructions, the historically "static"
> nature of compilers can be undone.
Thanks for the insight.
These technologies we are using in Accelerator device and not host CPU
interface. host-side is all about memory management, communication, and
expressing the workload. And workload like vDPU application to
offload ORAN 7.2 split for 5G RU device is much beyond packet
processing.
>
> Tom
>
>
> >
> > >
> > >
next prev parent reply other threads:[~2021-10-20 5:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 18:14 jerinj
2021-10-19 18:14 ` [dpdk-dev] [RFC PATCH 1/1] dwa: introduce dataplane workload accelerator subsystem jerinj
2021-10-19 19:08 ` [dpdk-dev] [RFC PATCH 0/1] Dataplane Workload Accelerator library Thomas Monjalon
2021-10-19 19:36 ` Jerin Jacob
2021-10-19 20:42 ` Stephen Hemminger
2021-10-20 5:25 ` Jerin Jacob
2021-10-19 20:42 ` Tom Herbert
2021-10-20 5:38 ` Jerin Jacob [this message]
2021-10-22 12:00 ` Elena Agostini
2021-10-22 13:39 ` Jerin Jacob
2021-10-25 7:35 ` Mattias Rönnblom
2021-10-25 9:03 ` Jerin Jacob
2021-10-29 11:57 ` Mattias Rönnblom
2021-10-29 15:51 ` Jerin Jacob
2021-10-31 9:18 ` Mattias Rönnblom
2021-10-31 14:01 ` Jerin Jacob
2021-10-31 19:34 ` Thomas Monjalon
2021-10-31 21:13 ` Jerin Jacob
2021-10-31 21:55 ` Thomas Monjalon
2021-10-31 22:19 ` 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=CALBAE1N-109WrGnYtB1_JRrMq-1sbchNvTw8O1T60KfobjWQyQ@mail.gmail.com \
--to=jerinjacobk@gmail.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=chethan@sipanda.io \
--cc=ciara.loftus@intel.com \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.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=felipe@sipanda.io \
--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=honnappa.nagarahalli@arm.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=jerinj@marvell.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=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=ruifeng.wang@arm.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=siva@sipanda.io \
--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=thomas@monjalon.net \
--cc=tom@herbertland.com \
--cc=tom@sipanda.io \
--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).