From: Stephen Hemminger <stephen@networkplumber.org>
To: David Aldrich <david.aldrich.ntml@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] How to receive jumbo packets?
Date: Wed, 5 Aug 2020 11:00:31 -0700 [thread overview]
Message-ID: <20200805110031.5d5604cc@hermes.lan> (raw)
In-Reply-To: <CAJK_iejF4rNE9PZx4SAQf3ejL=jb1Az7_yUWCbYKfOXtMt2aOQ@mail.gmail.com>
On Wed, 5 Aug 2020 18:38:01 +0100
David Aldrich <david.aldrich.ntml@gmail.com> wrote:
> Hi
>
> Our dpdk application uses dpdk-stable-18.11.9. It successfully receives udp
> packets <1500 octets, but does not correctly process larger udp packets.
>
> I don't know where to look. Is there a DPDK function that sets or takes the
> MTU size for reception?
>
> How would jumbo packets typically be supported on the Rx side?
>
> Best regards
> David
Did you configure larger mtu and enable jumbo in the rx_conf?
next prev parent reply other threads:[~2020-08-05 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 17:38 David Aldrich
2020-08-05 18:00 ` Stephen Hemminger [this message]
2020-08-06 13:49 ` David Aldrich
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=20200805110031.5d5604cc@hermes.lan \
--to=stephen@networkplumber.org \
--cc=david.aldrich.ntml@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).