From: "Rao, Nikhil" <nikhil.rao@intel.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
jerin.jacob@caviumnetworks.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eventdev: use new event enqueue in Rx adapter
Date: Sat, 14 Oct 2017 08:18:42 +0530 [thread overview]
Message-ID: <b1215047-a9c9-c70b-34c2-582c3e102c59@intel.com> (raw)
In-Reply-To: <1507833953-4396-1-git-send-email-pbhagavatula@caviumnetworks.com>
On 10/13/2017 12:15 AM, Pavan Nikhilesh wrote:
> When event Rx adapter uses software based packet transfer, event op is
> always RTE_EVENT_OP_NEW.
> By using rte_event_enqueue_new_burst API the underlying event devices
> driver can use it as a hint to optimize enqueue operation if possible.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> ---
> lib/librte_eventdev/rte_event_eth_rx_adapter.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/librte_eventdev/rte_event_eth_rx_adapter.c b/lib/librte_eventdev/rte_event_eth_rx_adapter.c
> index 1e42dde..fcba18d 100644
> --- a/lib/librte_eventdev/rte_event_eth_rx_adapter.c
> +++ b/lib/librte_eventdev/rte_event_eth_rx_adapter.c
> @@ -392,7 +392,7 @@ flush_event_buffer(struct rte_event_eth_rx_adapter *rx_adapter)
> &rx_adapter->event_enqueue_buffer;
> struct rte_event_eth_rx_adapter_stats *stats = &rx_adapter->stats;
>
> - uint16_t n = rte_event_enqueue_burst(rx_adapter->eventdev_id,
> + uint16_t n = rte_event_enqueue_new_burst(rx_adapter->eventdev_id,
> rx_adapter->event_port_id,
> buf->events,
> buf->count);
>
Reviewed-by: Nikhil Rao <nikhil.rao@intel.com>
next prev parent reply other threads:[~2017-10-14 2:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 18:45 Pavan Nikhilesh
2017-10-14 2:48 ` Rao, Nikhil [this message]
2017-10-16 11:35 ` 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=b1215047-a9c9-c70b-34c2-582c3e102c59@intel.com \
--to=nikhil.rao@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=pbhagavatula@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).