From: "Polehn, Mike A" <mike.a.polehn@intel.com>
To: Masaru OKI <oki+dpdk@chocot.jp>,
Saurabh Mishra <saurabh.globe@gmail.com>,
"users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-dev] rte_mbuf size for jumbo frame
Date: Tue, 26 Jan 2016 14:01:59 +0000 [thread overview]
Message-ID: <745DB4B8861F8E4B9849C970520ABBF149852DC7@ORSMSX102.amr.corp.intel.com> (raw)
In-Reply-To: <56A6A46C.1050003@chocot.jp>
Jumbo frames are generally handled by link lists (but called something else) of mbufs.
Enabling jumbo frames for the device driver should enable the right portion of the driver which handles the linked lists.
Don't make the mbufs huge.
Mike
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Masaru OKI
Sent: Monday, January 25, 2016 2:41 PM
To: Saurabh Mishra; users@dpdk.org; dev@dpdk.org
Subject: Re: [dpdk-dev] rte_mbuf size for jumbo frame
Hi,
1. Take care of unit size of mempool for mbuf.
2. Call rte_eth_dev_set_mtu() for each interface.
Note that some PMDs does not supported change MTU.
On 2016/01/26 6:02, Saurabh Mishra wrote:
> Hi,
>
> We wanted to use 10400 bytes size of each rte_mbuf to enable Jumbo frames.
> Do you guys see any problem with that? Would all the drivers like
> ixgbe, i40e, vmxnet3, virtio and bnx2x work with larger rte_mbuf size?
>
> We would want to avoid detailing with chained mbufs.
>
> /Saurabh
prev parent reply other threads:[~2016-01-26 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 21:02 [dpdk-users] " Saurabh Mishra
[not found] ` <56A6A46C.1050003@chocot.jp>
2016-01-26 14:01 ` Polehn, Mike A [this message]
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=745DB4B8861F8E4B9849C970520ABBF149852DC7@ORSMSX102.amr.corp.intel.com \
--to=mike.a.polehn@intel.com \
--cc=dev@dpdk.org \
--cc=oki+dpdk@chocot.jp \
--cc=saurabh.globe@gmail.com \
--cc=users@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).