From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id CA1DA282 for ; Wed, 14 Dec 2016 17:52:24 +0100 (CET) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga104.fm.intel.com with ESMTP; 14 Dec 2016 08:52:23 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,347,1477983600"; d="scan'208";a="42491575" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.64]) by fmsmga005.fm.intel.com with SMTP; 14 Dec 2016 08:52:21 -0800 Received: by (sSMTP sendmail emulation); Wed, 14 Dec 2016 16:52:21 +0000 Date: Wed, 14 Dec 2016 16:52:21 +0000 From: Bruce Richardson To: tom.barbette@ulg.ac.be Cc: dev@dpdk.org Message-ID: <20161214165220.GC110884@bricha3-MOBL3.ger.corp.intel.com> References: <415214732.17903310.1481728244157.JavaMail.zimbra@ulg.ac.be> <597694261.17905196.1481728433903.JavaMail.zimbra@ulg.ac.be> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <597694261.17905196.1481728433903.JavaMail.zimbra@ulg.ac.be> Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.7.1 (2016-10-04) Subject: Re: [dpdk-dev] No packets received if burst is too small in rte_eth_rx_burst 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: Wed, 14 Dec 2016 16:52:25 -0000 On Wed, Dec 14, 2016 at 04:13:53PM +0100, tom.barbette@ulg.ac.be wrote: > Hi list, > > Between 2.2.0 and 16.04 (up to at least 16.07.2 if not current), with the XL710 controller I do not get any packet when calling rte_eth_rx_burst if nb_pkts is too small. I would say smaller than 32. The input rate is not big, if that helps. But It should definitely get at least one packet per second. > > Any ideas? Is that a bug or expected behaviour? Could be caused by other ABI changes? > Does this issue still occur even if you disable the vector driver in your build-time configuration? /Bruce