From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <wei.zhao1@intel.com>
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120])
 by dpdk.org (Postfix) with ESMTP id 79045A49
 for <dev@dpdk.org>; Thu,  1 Nov 2018 04:12:24 +0100 (CET)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from fmsmga004.fm.intel.com ([10.253.24.48])
 by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
 31 Oct 2018 20:12:22 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.54,450,1534834800"; d="scan'208";a="102442895"
Received: from kmsmsx153.gar.corp.intel.com ([172.21.73.88])
 by fmsmga004.fm.intel.com with ESMTP; 31 Oct 2018 20:12:21 -0700
Received: from pgsmsx110.gar.corp.intel.com (10.221.44.111) by
 KMSMSX153.gar.corp.intel.com (172.21.73.88) with Microsoft SMTP Server (TLS)
 id 14.3.408.0; Thu, 1 Nov 2018 11:12:21 +0800
Received: from pgsmsx103.gar.corp.intel.com ([169.254.2.114]) by
 PGSMSX110.gar.corp.intel.com ([169.254.13.219]) with mapi id 14.03.0415.000;
 Thu, 1 Nov 2018 11:12:20 +0800
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>, "dev@dpdk.org"
 <dev@dpdk.org>
CC: Stephen Hemminger <stephen@networkplumber.org>
Thread-Topic: [dpdk-dev] Question about jumbo frame support on ixgbe
Thread-Index: AQHUcPL+b4YUk9Dok0W0EDja5ij6oqU6H1NwgAAf/aA=
Date: Thu, 1 Nov 2018 03:12:20 +0000
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07E68284@PGSMSX103.gar.corp.intel.com>
References: <20181031144907.303203-1-yong.liu@intel.com>
 <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 <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2018 03:12:25 -0000

Add Stephen Hemminger <stephen@networkplumber.org> for discussion.

> -----Original Message-----
> From: Zhao1, Wei
> Sent: Thursday, November 1, 2018 11:10 AM
> To: 'Hideyuki Yamashita' <yamashita.hideyuki@po.ntt-tx.co.jp>;
> dev@dpdk.org
> Subject: RE: [dpdk-dev] Question about jumbo frame support on ixgbe
>=20
> Hi,  Hideyuki Yamashita
>=20
>=20
> > -----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
> >
> > Hi,
> >
> > I have a very basic question about jumbo frame support for ixgbe.
> >
> > I understand that some drivers support jumbo frame and if it receive
> > jumbo packet (greater than 1500 byte), it creates mbuf chains and pass
> > it to DPDK application through e.g. rte_eth_rx_burst.
> >
> > However it looks that ixgbe driver does not support jumbo frame.
> >
> > Q1. Is my understanding above correct?
> > Q2. If A1 equals YES, then are there any future plan to support jumbo
> > frame on ixgbe?
>=20
> Your understanding above correct, but 82599 and x550 has support jumbo
> frame receive by now!
> In order to use this feature on ixgbe, you need do the following steps:
>=20
> 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_SCATTER bit in dev_conf.rxmode.offloads, this is the
> work of PMD driver when it detect jumbo frame is needed to be supported.
>=20
> 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!!
> If you not do this, you may only receive JUMBO frame but not forward out.
> Because as you say, the receive packets maybe has a mbuf chains(depending
> on the size relationship 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 que=
ue
> offloads bit!
>=20
> 3. enable it using CLI "port config mtu <port_id> <value>" if you are usi=
ng
> 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.
>=20
> And all my discussion is based on pf port, if you are using vf, we can ha=
ve a
> further discussion.
> Please feel free to contact me if necessary.
>=20
> >
> > BR,
> > Hideyuki Yamashita
> > NTT TechnoCross