From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <yamashita.hideyuki@po.ntt-tx.co.jp>
Received: from mail04.ics.ntt-tx.co.jp (mail05.ics.ntt-tx.co.jp
 [210.232.35.69]) by dpdk.org (Postfix) with ESMTP id E4EAA1D7
 for <dev@dpdk.org>; Wed, 31 Oct 2018 09:22:51 +0100 (CET)
Received: from gwchk03.silk.ntt-tx.co.jp (gwchk03.silk.ntt-tx.co.jp
 [10.107.0.111])
 by mail04.ics.ntt-tx.co.jp (unknown) with ESMTP id w9V8Mn2s008455
 for unknown; Wed, 31 Oct 2018 17:22:50 +0900
Received: (from root@localhost)
 by gwchk03.silk.ntt-tx.co.jp (unknown) id w9V8MnXL001966
 for unknown; Wed, 31 Oct 2018 17:22:49 +0900
Received: from gwchk.silk.ntt-tx.co.jp [10.107.0.110] 
 by gwchk03.silk.ntt-tx.co.jp with ESMTP id TAA01965;
 Wed, 31 Oct 2018 17:22:49 +0900
Received: from imss06.silk.ntt-tx.co.jp (localhost [127.0.0.1])
 by ccmail04.silk.ntt-tx.co.jp (unknown) with ESMTP id w9V8MnWx017555
 for unknown; Wed, 31 Oct 2018 17:22:49 +0900
Received: from imss06.silk.ntt-tx.co.jp (localhost [127.0.0.1])
 by imss06.silk.ntt-tx.co.jp (unknown) with ESMTP id w9V8Mnxr013259
 for unknown; Wed, 31 Oct 2018 17:22:49 +0900
Received: from ccmail04 (smtp03.silk.ntt-tx.co.jp [10.107.0.135]) by
 imss06.silk.ntt-tx.co.jp (unknown) with SMTP id w9V8MnQa013256 for unknown;
 Wed, 31 Oct 2018 17:22:49 +0900
Date: Wed, 31 Oct 2018 17:22:02 +0900
From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
In-Reply-To: <20181031144907.303203-1-yong.liu@intel.com>
References: <20181031144907.303203-1-yong.liu@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.74 [ja]
X-CCMail7: CC-Mail-V7.0.2-Client-Relayed
Message-Id: <201810310822.w9V8MaA1017463@ccmail04.silk.ntt-tx.co.jp>
X-TM-AS-MML: No
X-CC-Mail-RelayStamp: CC-Mail-V5.14-Server
To: dev@dpdk.org
Subject: [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: Wed, 31 Oct 2018 08:22:52 -0000

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?

BR,
Hideyuki Yamashita
NTT TechnoCross