From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id DD093D592 for ; Fri, 3 Mar 2017 12:20:25 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga105.fm.intel.com with ESMTP; 03 Mar 2017 03:20:24 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,236,1484035200"; d="scan'208";a="940194643" Received: from unknown (HELO dpdk5.bj.intel.com) ([172.16.182.182]) by orsmga003.jf.intel.com with ESMTP; 03 Mar 2017 03:20:23 -0800 From: Zhiyong Yang To: dev@dpdk.org Cc: bruce.richardson@intel.com Date: Fri, 3 Mar 2017 19:17:26 +0800 Message-Id: <1488539851-71009-1-git-send-email-zhiyong.yang@intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1487926101-4637-2-git-send-email-zhiyong.yang@intel.com> References: <1487926101-4637-2-git-send-email-zhiyong.yang@intel.com> Subject: [dpdk-dev] [PATCH v2 0/5] consistent PMD batching behaviour X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2017 11:20:26 -0000 The rte_eth_tx_burst() function in the file Rte_ethdev.h is invoked to transmit output packets on the output queue for DPDK applications as follows. static inline uint16_t rte_eth_tx_burst(uint8_t port_id, uint16_t queue_id, struct rte_mbuf **tx_pkts, uint16_t nb_pkts); Note: The fourth parameter nb_pkts: The number of packets to transmit. The rte_eth_tx_burst() function returns the number of packets it actually sent. Most of PMD drivers can support the policy "send as many packets to transmit as possible" at the PMD level. but the few of PMDs have some sort of artificial limits for the pkts sent successfully. For example, VHOST tx burst size is limited to 32 packets. Some rx_burst functions have the similar problem. The main benefit is consistent batching behavior for user to simplify their logic and avoid misusage at the application level, there is unified rte_eth_tx/rx_burst interface already, there is no reason for inconsistent behaviors. This patchset fixes it via adding wrapper function at the PMD level. Changes in V2: 1. rename ixgbe, i40e and fm10k vec function XXX_xmit_pkts_vec to new name XXX_xmit_fixed_burst_vec, new wrapper functions use original name XXX_xmit_pkts_vec according to Bruce's suggestion. 2. simplify the code to avoid the if or if/else. Zhiyong Yang (5): net/fm10k: remove limit of fm10k_xmit_pkts_vec burst size net/i40e: remove limit of i40e_xmit_pkts_vec burst size net/ixgbe: remove limit of ixgbe_xmit_pkts_vec burst size net/vhost: remove limit of vhost TX burst size net/vhost: remove limit of vhost RX burst size drivers/net/fm10k/fm10k.h | 4 ++-- drivers/net/fm10k/fm10k_ethdev.c | 28 ++++++++++++++++++++++++--- drivers/net/fm10k/fm10k_rxtx_vec.c | 4 ++-- drivers/net/i40e/i40e_rxtx.c | 28 ++++++++++++++++++++++++--- drivers/net/i40e/i40e_rxtx.h | 4 ++-- drivers/net/i40e/i40e_rxtx_vec_neon.c | 4 ++-- drivers/net/i40e/i40e_rxtx_vec_sse.c | 4 ++-- drivers/net/ixgbe/ixgbe_rxtx.c | 29 ++++++++++++++++++++++++++++ drivers/net/ixgbe/ixgbe_rxtx.h | 4 ++-- drivers/net/ixgbe/ixgbe_rxtx_vec_neon.c | 4 ++-- drivers/net/ixgbe/ixgbe_rxtx_vec_sse.c | 4 ++-- drivers/net/vhost/rte_eth_vhost.c | 34 +++++++++++++++++++++++++++++---- 12 files changed, 125 insertions(+), 26 deletions(-) -- 2.7.4