> -----Original Message----- > From: Jerin Jacob [mailto:jerin.ja...@caviumnetworks.com] > Sent: Wednesday, May 31, 2017 21:28 > To: Nipun Gupta <nipun.gu...@nxp.com> > Cc: dev@dpdk.org; Hemant Agrawal <hemant.agra...@nxp.com>; > harry.van.haa...@intel.com; bruce.richard...@intel.com; > gage.e...@intel.com; Shreyansh Jain <shreyansh.j...@nxp.com> > Subject: Re: [PATCH 20/20] doc: add NXP DPAA2 EVENTDEV details > > -----Original Message----- > > Date: Thu, 25 May 2017 23:37:51 +0530 > > From: Nipun Gupta <nipun.gu...@nxp.com> > > To: dev@dpdk.org > > CC: hemant.agra...@nxp.com, jerin.ja...@caviumnetworks.com, > > harry.van.haa...@intel.com, bruce.richard...@intel.com, > > gage.e...@intel.com, shreyansh.j...@nxp.com, Nipun Gupta > > <nipun.gu...@nxp.com> > > Subject: [PATCH 20/20] doc: add NXP DPAA2 EVENTDEV details > > X-Mailer: git-send-email 1.9.1 > > > > Signed-off-by: Nipun Gupta <nipun.gu...@nxp.com> > > --- > > MAINTAINERS | 1 + > > doc/guides/eventdevs/dpaa2.rst | 157 > +++++++++++++++++++++++++++++++++++++++++ > > 2 files changed, 158 insertions(+) > > create mode 100644 doc/guides/eventdevs/dpaa2.rst > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > index 45e284e..9c9095b 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -584,6 +584,7 @@ NXP DPAA2 Eventdev PMD > > M: Hemant Agrawal <hemant.agra...@nxp.com> > > M: Nipun Gupta <nipun.gu...@nxp.com> > > F: drivers/event/dpaa2/ > > +F: doc/guides/eventdevs/dpaa2.rst > > > > Packet processing > > ----------------- > > + > > +To compile the DPAA2 EVENTDEV PMD for Linux arm64 gcc target, run the > > +following ``make`` command: > > + > > +.. code-block:: console > > + > > + cd <DPDK-source-directory> > > + make config T=arm64-dpaa2-linuxapp-gcc install > > It nice to mention your PMD driver vdev name in the document. > > > + > > +Limitations > > +----------- > > + > > +Platform Requirement > > +~~~~~~~~~~~~~~~~~~~~ > > + > > +DPAA2 drivers for DPDK can only work on NXP SoCs as listed in the > > +``Supported DPAA2 SoCs``. > > + > > +Port-core binding > > +~~~~~~~~~~~~~~~~~ > > + > > +DPAA2 EVENTDEV driver requires event port 'x' to be used on core 'x'. > > Is it a HW limitation? or Is it like, only one port can connect to one > lcore. If it latter, then I think, you can have physical port to virtual > port translation in slow path as ports are enumerated as 0 to N. lcore > id can be anything.
Appreciate your suggestion, but right now our event driver limits this. This is because core needs to be known at event port setup. As event port setup is done at initialization time, we need to have this limitation. We are having discussions to somehow do away with this. Thanks, Nipun > > > > -- > > 1.9.1 > >
