From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Eads, Gage" <gage.eads@intel.com>,
"nipun.gupta@nxp.com" <nipun.gupta@nxp.com>,
"Vangati, Narender" <narender.vangati@intel.com>,
"Rao, Nikhil" <nikhil.rao@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] eventdev: introduce burst mode capabality
Date: Wed, 14 Jun 2017 11:21:40 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA640C2DC34@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20170614045733.10756-1-jerin.jacob@caviumnetworks.com>
> From: Jerin Jacob [mailto:jerin.jacob@caviumnetworks.com]
> Sent: Wednesday, June 14, 2017 5:58 AM
> To: dev@dpdk.org
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; Van Haaren, Harry
> <harry.van.haaren@intel.com>; hemant.agrawal@nxp.com; Eads, Gage <gage.eads@intel.com>;
> nipun.gupta@nxp.com; Vangati, Narender <narender.vangati@intel.com>; Rao, Nikhil
> <nikhil.rao@intel.com>; Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH 1/2] eventdev: introduce burst mode capabality
>
> Introducing the burst mode capability flag to express the event device
> is capable of operating in burst mode for enqueue(forward, release) and
> dequeue operation. If the device is not capable, then the application
> still uses the rte_event_dequeue_burst() and rte_event_enqueue_burst()
> but PMD accepts only one event at a time which is any way transparent
> with the current rte_event_*_burst API semantics.
<snip> details of changes
> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> ---
> lib/librte_eventdev/rte_eventdev.c | 10 ++++++----
> lib/librte_eventdev/rte_eventdev.h | 20 ++++++++++++++++----
> 2 files changed, 22 insertions(+), 8 deletions(-)
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
prev parent reply other threads:[~2017-06-14 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 4:57 Jerin Jacob
2017-06-14 4:57 ` [dpdk-dev] [PATCH 2/2] event/sw: advertise the burst mode capability Jerin Jacob
2017-06-14 11:22 ` Van Haaren, Harry
2017-06-20 14:15 ` Jerin Jacob
2017-06-14 11:21 ` Van Haaren, Harry [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=E923DB57A917B54B9182A2E928D00FA640C2DC34@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=narender.vangati@intel.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).