DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Daly, Dan" <dan.daly@intel.com>
Subject: Re: [dpdk-dev] [RFC] P4 enablement in DPDK
Date: Wed, 20 Jun 2018 11:56:38 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E75BD09@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20180620061258.GA31043@jerin>

<snip>

> 
> How about moving this as separate library(pipeline dev) with driver(plugin)
> interface
> and librte_pipeline based API being used as one plugin/driver. This will
> enable us
> to hook another HW based or HW-SW combination of plugins in future.

This is exactly what we are looking to do. The PDEV API is meant to be generic, while the current librte_pipeline API is limited to SW only. The intention is to transform the current librte_pipeline code into driver/plugin for the new PDEV API, with hopefully lots of other devices supporting PDEV through their own drivers.

> 
> Eventdev has capability to create pipeline that can be add in future
> as plugin/driver. The code to deal with rte_tm etc in plugin, you can
> make it as common code in the library. So that new plugin can be created
> based eventdev
> + other building blocks such as rte_tm.
> 

It would be great to be able to expose some/all of the eventdev features through PDEV API, let's look at this together.

> 
> /Jerin

      reply	other threads:[~2018-06-20 11:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 17:22 Cristian Dumitrescu
2018-04-19  5:04 ` Kuusisaari, Juhamatti
2018-06-15 23:25 ` antonin
2018-06-19 17:52   ` Dumitrescu, Cristian
2018-06-20  6:13 ` Jerin Jacob
2018-06-20 11:56   ` Dumitrescu, Cristian [this message]

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=3EB4FA525960D640B5BDFFD6A3D891268E75BD09@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dan.daly@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.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).