From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <NissimN@Radware.com> Received: from ILCAS1.corp.radware.com (mailout1.radware.com [192.115.180.130]) by dpdk.org (Postfix) with ESMTP id C9A0FB62 for <dev@dpdk.org>; Thu, 7 May 2015 16:43:51 +0200 (CEST) Received: from ILMB1.corp.radware.com ([169.254.1.165]) by ILCAS1.corp.radware.com ([176.200.120.121]) with mapi id 14.03.0210.002; Thu, 7 May 2015 17:43:48 +0300 From: Nissim Nisimov <NissimN@Radware.com> To: "'dev@dpdk.org'" <dev@dpdk.org> Thread-Topic: Intel fortville not working with multi-segment Thread-Index: AQHQiNQ5U2XgJ4AN/EuhMXX6NLfWqw== Date: Thu, 7 May 2015 14:43:47 +0000 Message-ID: <94AA676E9B9A384A844E7692F3CAD90642428A41@ILMB1.corp.radware.com> References: <94AA676E9B9A384A844E7692F3CAD906423BDF6F@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.120.205] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [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 <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 07 May 2015 14:43:52 -0000 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) I don't have support for TSO in my application. Do I need to turn the TSO f= or the NIC? Is it a known issue? any workaround for it? Thanks, Nissim