DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Nikhil Rao <nikhil.rao@intel.com>
Cc: bruce.richardson@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6 0/7] eventdev: cover letter: eth Rx adapter
Date: Tue, 10 Oct 2017 22:19:44 +0530	[thread overview]
Message-ID: <20171010164943.GA4910@jerin> (raw)
In-Reply-To: <1507674097-19597-1-git-send-email-nikhil.rao@intel.com>

-----Original Message-----
> Date: Wed, 11 Oct 2017 03:51:30 +0530
> From: Nikhil Rao <nikhil.rao@intel.com>
> To: jerin.jacob@caviumnetworks.com, bruce.richardson@intel.com
> CC: dev@dpdk.org
> Subject: [PATCH v6 0/7] eventdev: cover letter: eth Rx adapter
> X-Mailer: git-send-email 2.7.4
> 
> Eventdev-based networking applications require a component to dequeue
> packets from NIC Rx queues and inject them into eventdev queues[1]. While
> some platforms (e.g. Cavium Octeontx) do this operation in hardware, other
> platforms use software.
> 
> This patchset introduces an ethernet Rx event adapter that dequeues packets
> from ethernet devices and enqueues them to event devices. This patch is based on
> a previous RFC[2] and supercedes [3], the main difference being that
> this version implements a common abstraction for HW and SW based packet transfers.
> 
> The adapter is designed to work with the EAL service core[4] for SW based
> packet transfers. An eventdev PMD callback is used to determine that SW
> based packet transfer service is required. The application can discover
> and configure the service with a core mask using rte_service APIs.
> 
> The adapter can service multiple ethernet devices and queues. For SW based
> packet transfers each queue is  configured with a servicing weight to
> control the relative frequency with which the adapter polls the queue,
> and the event fields to use when constructing packet events. The adapter
> has two modes for programming an event's flow ID: use a static per-queue
> user-specified value or use the RSS hash.
> 
> A detailed description of the adapter is contained in the header's
> comments.
> 
> [1] http://dpdk.org/ml/archives/dev/2017-May/065341.html
> [2] http://dpdk.org/ml/archives/dev/2017-May/065539.html
> [3] http://dpdk.org/ml/archives/dev/2017-July/070452.html
> [4] http://dpdk.org/ml/archives/dev/2017-July/069782.html
> 
> v3:
> - This patch extends the V2 implementation with some changes to
> provide a common API across HW & SW packet transfer mechanisms from
> the eth devices to the event devices.
> - Introduces a caps API that is used by the apps and the Rx
> adapter to configure the packet transfer path.
> - Adds an API to retrieve the service ID of the service function.
> (if one is used by the adapter)
> 
> v4:
> - Unit test fixes (Santosh Shukla)
> - Pass ethernet device pointer to eventdev callback functions
> instead of ethernet port ID. (Nipun Gupta)
> - Check for existence of stats callback before invocation (Nipun Gupta)
> - Various code cleanups (Harry Van Haaren)
> 
> v5:
> - Add RTE_EVENT_TYPE_ETH_RX_ADAPTER (Jerin)
> - Add header to documentation build (Jerin)
> - Split patch series into smaller patches (Jerin)
> - Replace RTE_EVENT_ETH_RX_ADAPTER_CAP_FLOW_ID with
> RTE_EVENT_ETH_RX_ADAPTER_CAP_OVERRIDE_FLOW_ID (Jerin)
> - If eth_rx_adapter_caps_get PMD callback isn't implemented
> return zeored caps (Jerin)
> - Replace RTE_EVENT_ETH_RX_ADAPTER_CAP_SINGLE_EVENTQ with
> RTE_EVENT_ETH_RX_ADAPTER_CAP_MULTI_EVENTQ (Jerin)
> - Replace RTE_MAX_EVENT_ETH_RX_ADAPTER_INSTANCE with
> RTE_EVENT_ETH_RX_ADAPTER_MAX_INSTANCE (Jerin)
> - Move rss_key_be to per adapter memory
> - Various other fixes (Jerin)
> - Test fixes for mempool (Santosh)
> - Change order for event v/s eth port init in test app (Pavan)
> 
> v6:
> - Fixed out of scope variable in rte_event_eth_rx_adapter.c (Pavan)
> - Add #define for RSS_KEY_SIZE in rte_event_eth_rx_adapter.c (Pavan)
> - Doxygen and git log fixes (Jerin)
> 
> Nikhil Rao (7):

Applied to dpdk-next-eventdev/master. Thanks.

Please update the release notes and send the programmer guide document
as discussed.

  parent reply	other threads:[~2017-10-10 16:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 22:21 Nikhil Rao
2017-10-10 16:26 ` Jerin Jacob
2017-10-10 16:49 ` Jerin Jacob [this message]
2017-10-10 22:21 ` [dpdk-dev] [PATCH v6 1/7] eventdev: add caps API and PMD callback for " Nikhil Rao
2017-10-10 22:21 ` [dpdk-dev] [PATCH v6 2/7] eventdev: add PMD callbacks " Nikhil Rao
2017-10-10 22:21 ` [dpdk-dev] [PATCH v6 3/7] eventdev: add eth Rx adapter caps function to SW PMD Nikhil Rao
2017-10-10 23:16   ` Thomas Monjalon
2017-10-11  2:57     ` Jerin Jacob
2017-10-10 22:21 ` [dpdk-dev] [PATCH v6 4/7] eventdev: add eth Rx adapter API header Nikhil Rao
2017-10-10 22:21 ` [dpdk-dev] [PATCH v6 5/7] eventdev: add event type for eth Rx adapter Nikhil Rao
2017-10-10 22:21 ` [dpdk-dev] [PATCH v6 6/7] eventdev: add eth Rx adapter implementation Nikhil Rao
2017-10-10 22:21 ` [dpdk-dev] [PATCH v6 7/7] eventdev: add tests for eth Rx adapter APIs Nikhil Rao
2017-10-10 14:05   ` Jerin Jacob
2017-10-10 23:24     ` Nikhil Rao

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=20171010164943.GA4910@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=nikhil.rao@intel.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).