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 F0FC5A49 for ; Thu, 1 Nov 2018 04:16:52 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Oct 2018 20:16:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,450,1534834800"; d="scan'208";a="88584235" Received: from pgsmsx105.gar.corp.intel.com ([10.221.44.96]) by orsmga008.jf.intel.com with ESMTP; 31 Oct 2018 20:16:50 -0700 Received: from pgsmsx103.gar.corp.intel.com ([169.254.2.114]) by PGSMSX105.gar.corp.intel.com ([169.254.4.31]) with mapi id 14.03.0415.000; Thu, 1 Nov 2018 11:10:01 +0800 From: "Zhao1, Wei" To: Hideyuki Yamashita , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Question about jumbo frame support on ixgbe Thread-Index: AQHUcPL+b4YUk9Dok0W0EDja5ij6oqU6H1Nw Date: Thu, 1 Nov 2018 03:10:00 +0000 Message-ID: References: <20181031144907.303203-1-yong.liu@intel.com> <201810310822.w9V8MaA1017463@ccmail04.silk.ntt-tx.co.jp> In-Reply-To: <201810310822.w9V8MaA1017463@ccmail04.silk.ntt-tx.co.jp> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [172.30.20.206] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Question about jumbo frame support on ixgbe 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: Thu, 01 Nov 2018 03:16:53 -0000 Hi, Hideyuki Yamashita > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Hideyuki Yamashita > Sent: Wednesday, October 31, 2018 4:22 PM > To: dev@dpdk.org > Subject: [dpdk-dev] Question about jumbo frame support on ixgbe >=20 > Hi, >=20 > I have a very basic question about jumbo frame support for ixgbe. >=20 > I understand that some drivers support jumbo frame and if it receive jumb= o > packet (greater than 1500 byte), it creates mbuf chains and pass it to DP= DK > application through e.g. rte_eth_rx_burst. >=20 > However it looks that ixgbe driver does not support jumbo frame. >=20 > Q1. Is my understanding above correct? > Q2. If A1 equals YES, then are there any future plan to support jumbo fra= me > on ixgbe? Your understanding above correct, but 82599 and x550 has support jumbo fram= e receive by now! In order to use this feature on ixgbe, you need do the following steps: 1. you must set dev_conf.rxmode. max_rx_pkt_len to a big number, eg. 9500, = when doing port start, for example when start port in API rte_eth_dev_start= (). ixgbe_dev_rx_init() will chose a scatter receive function if the max_rx_pkt= _len is larger than the mbuf size, you do not need to set DEV_RX_OFFLOAD_SC= ATTER bit in=20 dev_conf.rxmode.offloads, this is the work of PMD driver when it detect jum= bo frame is needed to be supported. 2. set dev_conf.txmode.offloads bit of DEV_TX_OFFLOAD_MULTI_SEGS to 1 when= doing rte_eth_tx_queue_setup() or , this is very important!!=20 If you not do this, you may only receive JUMBO frame but not forward out. B= ecause as you say, the receive packets maybe has a mbuf chains(depending on the size relations= hip of mbuf size and the max_rx_pkt_len). But in ixgbe PMD for setting tx function, it is confusing in ixgbe_set_tx_= function(), you need to take care of it, it is based on queue offloads bit= ! 3. enable it using CLI "port config mtu " if you are using= testpmd or using API rte_eth_dev_set_mtu() for your own APP. The mtu number is just what you need to update for a large number. And all my discussion is based on pf port, if you are using vf, we can have= a further discussion. Please feel free to contact me if necessary. >=20 > BR, > Hideyuki Yamashita > NTT TechnoCross