From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <nikhil.rao@intel.com> Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id AB8851B335 for <dev@dpdk.org>; Sat, 14 Oct 2017 04:48:48 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Oct 2017 19:48:47 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.43,373,1503385200"; d="scan'208";a="1205713942" Received: from nikhilr-mobl.amr.corp.intel.com (HELO [10.252.73.110]) ([10.252.73.110]) by fmsmga001.fm.intel.com with ESMTP; 13 Oct 2017 19:48:44 -0700 To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>, jerin.jacob@caviumnetworks.com Cc: dev@dpdk.org References: <1507833953-4396-1-git-send-email-pbhagavatula@caviumnetworks.com> From: "Rao, Nikhil" <nikhil.rao@intel.com> Message-ID: <b1215047-a9c9-c70b-34c2-582c3e102c59@intel.com> Date: Sat, 14 Oct 2017 08:18:42 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <1507833953-4396-1-git-send-email-pbhagavatula@caviumnetworks.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] eventdev: use new event enqueue in Rx adapter X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Sat, 14 Oct 2017 02:48:49 -0000 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>