From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id D97D1C37E for ; Mon, 11 May 2015 04:03:30 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP; 10 May 2015 19:03:29 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,403,1427785200"; d="scan'208";a="723758091" Received: from pgsmsx102.gar.corp.intel.com ([10.221.44.80]) by fmsmga002.fm.intel.com with ESMTP; 10 May 2015 19:03:28 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by PGSMSX102.gar.corp.intel.com (10.221.44.80) with Microsoft SMTP Server (TLS) id 14.3.224.2; Mon, 11 May 2015 10:02:27 +0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.162]) by SHSMSX101.ccr.corp.intel.com ([10.239.4.153]) with mapi id 14.03.0224.002; Mon, 11 May 2015 10:02:25 +0800 From: "Zhang, Helin" To: Nissim Nisimov , "'dev@dpdk.org'" Thread-Topic: Intel fortville not working with multi-segment Thread-Index: AQHQiNQ/xilfK9NqzkGx1SGsGrsiU511okEQgABoB4A= Date: Mon, 11 May 2015 02:02:24 +0000 Message-ID: References: <94AA676E9B9A384A844E7692F3CAD906423BDF6F@ILMB1.corp.radware.com> <94AA676E9B9A384A844E7692F3CAD90642428A41@ILMB1.corp.radware.com> <94AA676E9B9A384A844E7692F3CAD90642432170@ILMB1.corp.radware.com> In-Reply-To: <94AA676E9B9A384A844E7692F3CAD90642432170@ILMB1.corp.radware.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Intel fortville not working with multi-segment 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: Mon, 11 May 2015 02:03:31 -0000 Hi Nissim Are you using PF pass-through or VF pass-through? For PF pass-through, you might have already gotten the fix. For VF pass-through, there is a bug fix which is needed for supporting jumb= o frame and multiple mbuf. http://www.dpdk.org/dev/patchwork/patch/4641/ Regards, Helin > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Nissim Nisimov > Sent: Monday, May 11, 2015 3:48 AM > To: Nissim Nisimov; 'dev@dpdk.org' > Subject: Re: [dpdk-dev] Intel fortville not working with multi-segment >=20 > Hi, >=20 > can someone assist regarding this issue? >=20 > Is it a known limitation in i40e/dpdk (no support for multi-segment)? >=20 > Thx > Nissim >=20 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Nissim Nisimov > Sent: Thursday, May 07, 2015 5:44 PM > To: 'dev@dpdk.org' > Subject: [dpdk-dev] Intel fortville not working with multi-segment >=20 > Hi, >=20 >=20 >=20 > I am trying to work with Intel Fortville (XL710) NICs in Passthrough mode > from a VM running dpdk app. >=20 >=20 > First I didn't have any TX traffic from the VM, I got dpdk patch for this= issue > and it fixed it. (http://www.dpdk.org/dev/patchwork/patch/4588/) >=20 > But now I see that when trying to run multi-segment traffic not all the > packets reaching the VM (I tested it on bare metal as well and saw the > same issue) >=20 > Is it a known issue? any workaround for it? >=20 > Thanks, > Nissim