From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by dpdk.org (Postfix) with ESMTP id B26AE12A8 for ; Fri, 9 Jan 2015 07:46:01 +0100 (CET) Received: from jaguar.aricent.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 84FD9218B87; Fri, 9 Jan 2015 12:16:00 +0530 (IST) Received: from GURCASV02.AD.ARICENT.COM (unknown [10.203.26.93]) by jaguar.aricent.com (Postfix) with ESMTPS id 6E2F4218B7E; Fri, 9 Jan 2015 12:16:00 +0530 (IST) Received: from GURMBXV02.AD.ARICENT.COM (10.203.26.97) by GURMBXV03.AD.ARICENT.COM (10.203.26.98) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 9 Jan 2015 12:15:58 +0530 Received: from GURMBXV02.AD.ARICENT.COM ([10.203.26.97]) by GURMBXV02.AD.ARICENT.COM ([169.254.4.239]) with mapi id 15.00.0847.030; Fri, 9 Jan 2015 12:15:58 +0530 From: Prashant Upadhyaya To: Bruce Richardson , Prashant Upadhyaya Thread-Topic: [dpdk-dev] Packet Rx issue with DPDK1.8 Thread-Index: AQHQKxqjyDQ3n8HYu0+gdFPViF2RRJy14OCAgAF4I6A= Date: Fri, 9 Jan 2015 06:45:57 +0000 Message-ID: References: <20150108134728.GA2536@bricha3-MOBL3> In-Reply-To: <20150108134728.GA2536@bricha3-MOBL3> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [122.161.157.236] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-MML: disable Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Packet Rx issue with DPDK1.8 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2015 06:46:02 -0000 Hi Bruce, I tried with your suggestion. When I disable the _vec function with the following config change, the usec= ase works for me. So it points to some issue in the _vec function. CONFIG_RTE_IXGBE_INC_VECTOR=3Dy, I changed this parameter to CONFIG_RTE_IXG= BE_INC_VECTOR=3Dn There appears to be some gottcha in the function therefore, somebody may wa= nt to run some tests again perhaps with jumbo frames enabled (and sending s= mall normal frames) Regards -Prashant -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson Sent: Thursday, January 08, 2015 7:17 PM To: Prashant Upadhyaya Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Packet Rx issue with DPDK1.8 On Thu, Jan 08, 2015 at 01:40:54PM +0530, Prashant Upadhyaya wrote: > Hi, > > I am migrating from DPDK1.7 to DPDK1.8. > My application works fine with DPDK1.7. > I am using 10 Gb Intel 82599 NIC. > I have jumbo frames enabled, with max_rx_pkt_len =3D 10232 My mbuf > dataroom size is 2048+headroom So naturally the > ixgbe_recv_scattered_pkts driver function is triggered for receiving. > This works with DPDK1.7 and my app receives packets. > However, it does not work with DPDK1.8 somehow.I don't receive any packet= s. > > So, I increased the mbuf data room size in my application to a higher > value so that the function ixgbe_recv_scattered_pkts is not enabled (I > believe ixgbe_recv_pkts will be used in this case), and now my > application starts getting packets with DPDK1.8 and the entire > application usecase works fine (ofcourse my application had to adapt > to the mbuf structure changes which I have done) > > I am kind of coming to the conclusion that ixgbe_recv_scattered_pkts > has something broken in DPDK1.8 as compared to the earlier versions by > the above empirical evidence. > > Has anybody else faced a similar issue ? > > Regards > -Prashant This is worrying to hear. In 1.8, there is now the receive_scattered_pkts_v= ec function which manages changed mbufs. This was tested - both in developm= ent and in validation - before release, but since it's new code, it's entir= ely possible we missed something. Can you perhaps try disabling the vector = driver in 1.8, and see if receiving scattered packets/chained mbufs works? Regards, /Bruce "DISCLAIMER: This message is proprietary to Aricent and is intended solely = for the use of the individual to whom it is addressed. It may contain privi= leged or confidential information and should not be circulated or used for = any purpose other than for what it is intended. If you have received this m= essage in error, please notify the originator immediately. If you are not t= he intended recipient, you are notified that you are strictly prohibited fr= om using, copying, altering, or disclosing the contents of this message. Ar= icent accepts no responsibility for loss or damage arising from the use of = the information transmitted by this email including damage from virus."