From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id F0FA31C62F for ; Fri, 13 Apr 2018 16:52:24 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Apr 2018 07:52:23 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,445,1517904000"; d="scan'208";a="33153680" Received: from irsmsx110.ger.corp.intel.com ([163.33.3.25]) by orsmga007.jf.intel.com with ESMTP; 13 Apr 2018 07:52:23 -0700 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.176]) by irsmsx110.ger.corp.intel.com ([169.254.15.211]) with mapi id 14.03.0319.002; Fri, 13 Apr 2018 15:52:21 +0100 From: "Stokes, Ian" To: "dev@dpdk.org" Thread-Topic: DEV_RX_OFFLOAD_SCATTER for ixgbe and igb devices Thread-Index: AdPTNwIEG0Bw74VVTu+z3yivWQp4lA== Date: Fri, 13 Apr 2018 14:52:22 +0000 Message-ID: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiM2M1NjEwZmUtMjhhOS00Zjg0LWE5NTEtYTlkZTk3ZjQ2ZjU1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJmK1J2V2l5Q1djMlJzM01iXC95YjlDY1lKcEcxYXJVR3ZvSXBnY0FLVld5aWxyeG1Iakw4d2l3SlJDYUIrUzEwciJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [dpdk-dev] DEV_RX_OFFLOAD_SCATTER for ixgbe and igb devices 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: Fri, 13 Apr 2018 14:52:26 -0000 Hi all, Currently it's the case that for some NICs (e.g. igb driver or ixgbe driver= based), scatter_rx needs to be enabled explicitly in the case where it was= not configured before. A patch submitted for ovs-dpdk proposes to check that the DEV_RX_OFFLOAD_SC= ATTER flag is present in rte_ethdev_info.rx_offload_capa before setting sca= tter_rx. https://mail.openvswitch.org/pipermail/ovs-dev/2018-April/345901.html While testing igb and ixgbe devices I spotted the DEV_RX_OFFLOAD_SCATTER fl= ag is not set in rx_offload_capa. As these devices require scatter_rx, should the scatter_rx flag be set for = them as part of the eth_igb_infos_get() for igb and ixgbe_dev_info_get for = ixgbe? Thanks Ian=20 =20