From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id A72041B69B for ; Sat, 9 Feb 2019 14:51:56 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Feb 2019 05:51:55 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,351,1544515200"; d="scan'208";a="132278989" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by FMSMGA003.fm.intel.com with ESMTP; 09 Feb 2019 05:51:55 -0800 Received: from fmsmsx156.amr.corp.intel.com (10.18.116.74) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sat, 9 Feb 2019 05:51:55 -0800 Received: from fmsmsx117.amr.corp.intel.com ([169.254.3.143]) by fmsmsx156.amr.corp.intel.com ([169.254.13.157]) with mapi id 14.03.0415.000; Sat, 9 Feb 2019 05:51:55 -0800 From: "Wiles, Keith" To: Filip Janiszewski CC: "users@dpdk.org" Thread-Topic: [dpdk-users] RX of multi-segment jumbo frames Thread-Index: AQHUwGgyeG5oDlToQUuXamursyiZkKXYAoeA Date: Sat, 9 Feb 2019 13:51:54 +0000 Message-ID: <95B2277E-2E64-4703-97C3-022967A7F175@intel.com> References: <4bd38b68-02e7-f031-5627-2bd2c9a38333@filipjaniszewski.com> In-Reply-To: <4bd38b68-02e7-f031-5627-2bd2c9a38333@filipjaniszewski.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.255.229.89] Content-Type: text/plain; charset="us-ascii" Content-ID: <84089E8209F07A4D8E921601912BD1DB@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] RX of multi-segment jumbo frames X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2019 13:51:57 -0000 > On Feb 9, 2019, at 5:11 AM, Filip Janiszewski wrote: >=20 > Hi, >=20 > I'm attempting to receive jumbo frames (~9000 bytes) on a Mellonox card > using DPDK, I've configured the DEV_RX_OFFLOAD_JUMBO_FRAME offload for > rte_eth_conf and rte_eth_rxconf (per RX Queue), but I can capture jumbo > frames only if the mbuf is large enough to contain the whole packet, is > there a way to enable DPDK to chain the incoming data in mbufs smaller > than the actual packet? >=20 > We don't have many of those big packets coming in, so would be optimal > to leave the mbuf size to RTE_MBUF_DEFAULT_BUF_SIZE and then configure > the RX device to chain those bufs for larger packets, but can't find a > way to do it, any suggestion? >=20 the best i understand is the nic or pmd needs to be configured to split up = packets between mbufs in the rx ring. i look in the docs for the nic and se= e if it supports splitting up packets or ask the maintainer from the mainta= iners file. > Thanks >=20 > --=20 > BR, Filip > +48 666 369 823 Regards, Keith