All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Gage Eads <gage.eads@intel.com>
Cc: dev@dpdk.org, harry.van.haaren@intel.com,
	bruce.richardson@intel.com, hemant.agrawal@nxp.com,
	nipun.gupta@nxp.com, santosh.shukla@caviumnetworks.com
Subject: Re: [PATCH v2 1/2] eventdev: add implicit release disable capability
Date: Sat, 16 Dec 2017 14:20:46 +0530	[thread overview]
Message-ID: <20171216085044.GA8023@jerin> (raw)
In-Reply-To: <1513014992-10861-1-git-send-email-gage.eads@intel.com>

-----Original Message-----
> Date: Mon, 11 Dec 2017 11:56:31 -0600
> From: Gage Eads <gage.eads@intel.com>
> To: dev@dpdk.org
> CC: jerin.jacob@caviumnetworks.com, harry.van.haaren@intel.com,
>  bruce.richardson@intel.com, hemant.agrawal@nxp.com, nipun.gupta@nxp.com,
>  santosh.shukla@caviumnetworks.com
> Subject: [PATCH v2 1/2] eventdev: add implicit release disable capability
> X-Mailer: git-send-email 2.7.4
> 
> This commit introduces a capability for disabling the "implicit" release
> functionality for a port, which prevents the eventdev PMD from issuing
> outstanding releases for previously dequeued events when dequeuing a new
> batch of events.
> 
> If a PMD does not support this capability, the application will receive an
> error if it attempts to setup a port with implicit releases disabled.
> Otherwise, if the port is configured with implicit releases disabled, the
> application must release each dequeued event by invoking
> rte_event_enqueue_burst() with RTE_EVENT_OP_RELEASE or
> RTE_EVENT_OP_FORWARD.
> 
> Signed-off-by: Gage Eads <gage.eads@intel.com>
> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>

With respect to specification changes:
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>

  parent reply	other threads:[~2017-12-16  8:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30  4:20 [PATCH 0/2] add implicit release disable capability Gage Eads
2017-11-30  4:20 ` [PATCH 1/2] eventdev: " Gage Eads
2017-12-11 12:36   ` Van Haaren, Harry
2017-12-11 17:39     ` Eads, Gage
2017-12-11 17:56   ` [PATCH v2 " Gage Eads
2017-12-11 17:56     ` [PATCH v2 2/2] event/sw: simplify credit scheme Gage Eads
2017-12-16  8:50     ` Jerin Jacob [this message]
2017-11-30  4:20 ` [PATCH " Gage Eads
2017-12-11 13:42   ` Van Haaren, Harry
2017-12-16  8:54     ` Jerin Jacob

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=20171216085044.GA8023@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gage.eads@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=nipun.gupta@nxp.com \
    --cc=santosh.shukla@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.