From: "Wiles, Keith" <keith.wiles@intel.com>
To: Filip Janiszewski <contact@filipjaniszewski.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] RX of multi-segment jumbo frames
Date: Sat, 9 Feb 2019 13:51:54 +0000 [thread overview]
Message-ID: <95B2277E-2E64-4703-97C3-022967A7F175@intel.com> (raw)
In-Reply-To: <4bd38b68-02e7-f031-5627-2bd2c9a38333@filipjaniszewski.com>
> On Feb 9, 2019, at 5:11 AM, Filip Janiszewski <contact@filipjaniszewski.com> wrote:
>
> Hi,
>
> I'm attempting to receive jumbo frames (~9000 bytes) on a Mellonox card
> using DPDK, I've configured the DEV_RX_OFFLOAD_JUMBO_FRAME offload for
> rte_eth_conf and rte_eth_rxconf (per RX Queue), but I can capture jumbo
> frames only if the mbuf is large enough to contain the whole packet, is
> there a way to enable DPDK to chain the incoming data in mbufs smaller
> than the actual packet?
>
> We don't have many of those big packets coming in, so would be optimal
> to leave the mbuf size to RTE_MBUF_DEFAULT_BUF_SIZE and then configure
> the RX device to chain those bufs for larger packets, but can't find a
> way to do it, any suggestion?
>
the best i understand is the nic or pmd needs to be configured to split up packets between mbufs in the rx ring. i look in the docs for the nic and see if it supports splitting up packets or ask the maintainer from the maintainers file.
> Thanks
>
> --
> BR, Filip
> +48 666 369 823
Regards,
Keith
next prev parent reply other threads:[~2019-02-09 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 11:11 Filip Janiszewski
2019-02-09 13:51 ` Wiles, Keith [this message]
2019-02-09 15:27 ` Filip Janiszewski
2019-02-09 15:36 ` Wiles, Keith
2019-02-15 5:59 ` Filip Janiszewski
2019-02-15 13:30 ` Wiles, Keith
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=95B2277E-2E64-4703-97C3-022967A7F175@intel.com \
--to=keith.wiles@intel.com \
--cc=contact@filipjaniszewski.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).