DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
To: dev@dpdk.org
Subject: [dpdk-dev] Question about jumbo frame support on ixgbe
Date: Wed, 31 Oct 2018 17:22:02 +0900	[thread overview]
Message-ID: <201810310822.w9V8MaA1017463@ccmail04.silk.ntt-tx.co.jp> (raw)
In-Reply-To: <20181031144907.303203-1-yong.liu@intel.com>

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

  reply	other threads:[~2018-10-31  8:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 14:49 [dpdk-dev] [PATCH] Doc: add known issue for restricted vdev ethdev ops in secondary process Marvin Liu
2018-10-31  8:22 ` Hideyuki Yamashita [this message]
2018-10-31 15:48   ` [dpdk-dev] Question about jumbo frame support on ixgbe Stephen Hemminger
2018-11-01  3:27     ` Zhao1, Wei
2018-11-01  6:55     ` Zhao1, Wei
2018-11-01  3:10   ` Zhao1, Wei
2018-11-02  1:38     ` Hideyuki Yamashita
2018-11-05  9:47       ` Zhao1, Wei
2018-11-01  3:12   ` Zhao1, Wei
2018-11-22 18:07 ` [dpdk-dev] [PATCH] Doc: add known issue for restricted vdev ethdev ops in secondary process Mcnamara, John
2018-11-23  2:07   ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201810310822.w9V8MaA1017463@ccmail04.silk.ntt-tx.co.jp \
    --to=yamashita.hideyuki@po.ntt-tx.co.jp \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).