From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ILCAS1.corp.radware.com (mailout1.radware.com [192.115.180.130]) by dpdk.org (Postfix) with ESMTP id C932EC386 for ; Sun, 10 May 2015 21:48:05 +0200 (CEST) Received: from ILMB1.corp.radware.com ([169.254.1.153]) by ILCAS1.corp.radware.com ([176.200.120.121]) with mapi id 14.03.0210.002; Sun, 10 May 2015 22:48:04 +0300 From: Nissim Nisimov To: Nissim Nisimov , "'dev@dpdk.org'" Thread-Topic: Intel fortville not working with multi-segment Thread-Index: AQHQiNQ/xilfK9NqzkGx1SGsGrsiU511okEQ Date: Sun, 10 May 2015 19:48:03 +0000 Message-ID: <94AA676E9B9A384A844E7692F3CAD90642432170@ILMB1.corp.radware.com> References: <94AA676E9B9A384A844E7692F3CAD906423BDF6F@ILMB1.corp.radware.com> <94AA676E9B9A384A844E7692F3CAD90642428A41@ILMB1.corp.radware.com> In-Reply-To: <94AA676E9B9A384A844E7692F3CAD90642428A41@ILMB1.corp.radware.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [176.200.121.206] 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: Sun, 10 May 2015 19:48:06 -0000 Hi, can someone assist regarding this issue? Is it a known limitation in i40e/dpdk (no support for multi-segment)? Thx Nissim -----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 Hi, I am trying to work with Intel Fortville (XL710) NICs in Passthrough mode f= rom a VM running dpdk app. First I didn't have any TX traffic from the VM, I got dpdk patch for this i= ssue and it fixed it. (http://www.dpdk.org/dev/patchwork/patch/4588/) But now I see that when trying to run multi-segment traffic not all the pac= kets reaching the VM (I tested it on bare metal as well and saw the same is= sue) Is it a known issue? any workaround for it? Thanks, Nissim