DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Anoob Joseph <anoobj@marvell.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	"Nicolau, Radu" <radu.nicolau@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Narayana Prasad Raju Athreya <pathreya@marvell.com>,
	Lukas Bartosik <lbartosik@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC PATCH 00/13] add eventmode to ipsec-secgw
Date: Fri, 25 Oct 2019 09:39:38 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725801A8C700A4@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <MN2PR18MB2877FEB821AD83A6ECD8DF68DF650@MN2PR18MB2877.namprd18.prod.outlook.com>


<snip>

> > >
> > > This series is targeted for next release (20.02). This series doesn't
> > > introduce any library change.
> >
> > By 'library change' you mean that this new event-mode will be supported
> > only by legacy code-path or ...?
> 
> [Anoob] All the changes are confined to 'examples/ipsec-secgw' directory. Right now, the worker threads make use of the existing
> routines in non-librte_ipsec mode.

And as I understand, you don't plan to use/support library mode?
I suppose I need to look to the actual code to understand more here.

> 
> >
> > >And the decision to add eventmode additions in ipsec-secgw  was
> > >approved by the Tech Board.
> > >
> > > Following are missing in the RFC. Will add it when sending patches.
> > > 1. Documentation.
> > > 2. More cleanup is needed. There are options that are added so that future
> > >    expansion is not hindered. Need inputs from the community if there is
> > use
> > >    case for them.
> > >
> > > Following are planned features,
> > > 1. Add burst mode workers.
> > > 2. Add non tx internal port worker.
> > > 3. Verify support for Rx core (the support is added but lack of h/w to
> > verify).
> > > 4. Add lookaside protocol support.
> > >
> > > Following are features that Marvell won't be attempting.
> > > 1. Inline crypto support.
> > > 2. Lookaside crypto support.
> >
> > Ok so what mode is supported right now with this RFC?
> 
> [Anoob] Inline protocol support is added with the RFC.

Ok..., but  do we have within DPDK any PMD that implements inline-proto?
AFAIK we don't, but might be I am missing something?

> 
> >
> > >
> > > For the features that Marvell won't be attempting, new workers can be
> > > introduced by the respective stake holders.
> > >
> > > Anoob Joseph (13):
> > >   examples/ipsec-secgw: add framework for eventmode helper
> > >   examples/ipsec-secgw: add eventdev port-lcore link
> > >   examples/ipsec-secgw: add Rx adapter support
> > >   examples/ipsec-secgw: add Tx adapter support
> > >   examples/ipsec-secgw: add routines to display config
> > >   examples/ipsec-secgw: add routines to launch workers
> > >   examples/ipsec-secgw: add support for internal ports
> > >   examples/ipsec-secgw: add eventmode to ipsec-secgw
> > >   examples/ipsec-secgw: add app inbound worker
> > >   examples/ipsec-secgw: add app processing code
> > >   examples/ipsec-secgw: add driver outbound worker
> > >   examples/ipsec-secgw: add app outbound worker
> > >   examples/ipsec-secgw: add cmd line option for bufs
> > >
> > >  examples/ipsec-secgw/Makefile       |    2 +
> > >  examples/ipsec-secgw/event_helper.c | 1757
> > > +++++++++++++++++++++++++++++++++++
> > >  examples/ipsec-secgw/event_helper.h |  334 +++++++
> > > examples/ipsec-secgw/ipsec-secgw.c  |  436 +++++++--
> > >  examples/ipsec-secgw/ipsec-secgw.h  |   81 ++
> > >  examples/ipsec-secgw/ipsec.c        |    4 +
> > >  examples/ipsec-secgw/ipsec.h        |   30 +-
> > >  examples/ipsec-secgw/ipsec_worker.c |  766 +++++++++++++++
> > >  examples/ipsec-secgw/ipsec_worker.h |   39 +
> > >  examples/ipsec-secgw/meson.build    |    4 +-
> > >  examples/ipsec-secgw/sa.c           |   11 -
> > >  11 files changed, 3360 insertions(+), 104 deletions(-)  create mode
> > > 100644 examples/ipsec-secgw/event_helper.c
> > >  create mode 100644 examples/ipsec-secgw/event_helper.h
> > >  create mode 100644 examples/ipsec-secgw/ipsec-secgw.h
> > >  create mode 100644 examples/ipsec-secgw/ipsec_worker.c
> > >  create mode 100644 examples/ipsec-secgw/ipsec_worker.h
> > >
> > > --
> > > 2.7.4


  reply	other threads:[~2019-10-25  9:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 15:10 Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 01/13] examples/ipsec-secgw: add framework for eventmode helper Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 02/13] examples/ipsec-secgw: add eventdev port-lcore link Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 03/13] examples/ipsec-secgw: add Rx adapter support Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 04/13] examples/ipsec-secgw: add Tx " Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 05/13] examples/ipsec-secgw: add routines to display config Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 06/13] examples/ipsec-secgw: add routines to launch workers Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 07/13] examples/ipsec-secgw: add support for internal ports Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 08/13] examples/ipsec-secgw: add eventmode to ipsec-secgw Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 09/13] examples/ipsec-secgw: add app inbound worker Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 10/13] examples/ipsec-secgw: add app processing code Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 11/13] examples/ipsec-secgw: add driver outbound worker Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 12/13] examples/ipsec-secgw: add app " Anoob Joseph
2019-10-09 15:10 ` [dpdk-dev] [RFC PATCH 13/13] examples/ipsec-secgw: add cmd line option for bufs Anoob Joseph
2019-10-16 13:02 ` [dpdk-dev] [RFC PATCH 00/13] add eventmode to ipsec-secgw Ananyev, Konstantin
2019-10-25  6:31   ` Anoob Joseph
2019-10-25  9:39     ` Ananyev, Konstantin [this message]
2019-10-28  5:44       ` Anoob Joseph

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=2601191342CEEE43887BDE71AB97725801A8C700A4@IRSMSX104.ger.corp.intel.com \
    --to=konstantin.ananyev@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=lbartosik@marvell.com \
    --cc=pathreya@marvell.com \
    --cc=radu.nicolau@intel.com \
    --cc=thomas@monjalon.net \
    /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).