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, hemant.agrawal@nxp.com,
	nipun.gupta@nxp.com
Subject: Re: [dpdk-dev] [PATCH v5 0/7] eventdev: cover letter: eth Rx adapter
Date: Mon, 9 Oct 2017 18:12:48 +0530	[thread overview]
Message-ID: <20171009124247.GG654@jerin> (raw)
In-Reply-To: <1507324201-3517-1-git-send-email-nikhil.rao@intel.com>

-----Original Message-----
> Date: Sat, 7 Oct 2017 02:39:54 +0530
> From: Nikhil Rao <nikhil.rao@intel.com>
> To: jerin.jacob@caviumnetworks.com, bruce.richardson@intel.com
> CC: dev@dpdk.org
> Subject: [PATCH v5 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.

Hi Nikhil,

- Please re base to dpdk-next-eventdev
- There is one check-git-long error. Please fix it
Wrong headline lowercase:
	eventdev: add event type for eth rx adapter
- You are planning to send the programmer guide with version. Right?
Are planning to send now or post RC1 ?

- For it looks OK to pull in next-eventdev, after fixing the
http://dpdk.org/ml/archives/dev/2017-October/077915.html and exiting
comments

CC: Hemant Agrawal <hemant.agrawal@nxp.com>
CC: Nipun Gupta <nipun.gupta@nxp.com>

Does any have any objection to pull this in RC1 if Nikhil sends the next
version in time?

  parent reply	other threads:[~2017-10-09 12:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 21:09 Nikhil Rao
2017-10-06 21:09 ` [dpdk-dev] [PATCH v5 1/7] eventdev: add caps API and PMD callback for " Nikhil Rao
2017-10-09 12:03   ` Jerin Jacob
2017-10-06 21:09 ` [dpdk-dev] [PATCH v5 2/7] eventdev: add PMD callbacks " Nikhil Rao
2017-10-09 12:05   ` Jerin Jacob
2017-10-06 21:09 ` [dpdk-dev] [PATCH v5 3/7] eventdev: add eth Rx adapter caps function to SW PMD Nikhil Rao
2017-10-09 12:06   ` Jerin Jacob
2017-10-06 21:09 ` [dpdk-dev] [PATCH v5 4/7] eventdev: add eth Rx adapter API header Nikhil Rao
2017-10-09 12:27   ` Jerin Jacob
2017-10-06 21:09 ` [dpdk-dev] [PATCH v5 5/7] eventdev: add event type for eth rx adapter Nikhil Rao
2017-10-09 12:31   ` Jerin Jacob
2017-10-06 21:10 ` [dpdk-dev] [PATCH v5 6/7] eventdev: add eth Rx adapter implementation Nikhil Rao
2017-10-06 14:34   ` Pavan Nikhilesh Bhagavatula
2017-10-06 21:10 ` [dpdk-dev] [PATCH v5 7/7] eventdev: add tests for eth Rx adapter APIs Nikhil Rao
2017-10-09 12:33   ` Jerin Jacob
2017-10-09 12:42 ` Jerin Jacob [this message]
2017-10-09 13:06   ` [dpdk-dev] [PATCH v5 0/7] eventdev: cover letter: eth Rx adapter Nipun Gupta

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=20171009124247.GG654@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=nikhil.rao@intel.com \
    --cc=nipun.gupta@nxp.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).