DPDK usage discussions
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
	"henning.schild@siemens.com" <henning.schild@siemens.com>
Subject: [dpdk-users] Jumbo packets get segmented on RX
Date: Tue, 27 Oct 2020 13:56:27 +0000	[thread overview]
Message-ID: <AM0PR10MB19399D173D14868A0BC2306D89160@AM0PR10MB1939.EURPRD10.PROD.OUTLOOK.COM> (raw)

Hi,

I'm trying to send and receive jumbo frame ethernet packets.
While sending works without any issues, I always receive fragmented / segmented packets.

This leads me to the following questions:

  1.  Is it possible to receive a frame without segmentation
  2.  How to properly size the mempool elements. Here, I tried the following (pkt_bytes is the maximum expected frame size):

buf_size = RTE_PKTMBUF_HEADROOM + pkt_bytes;
rte_mempool_create(mempool_name, NB_MBUF, buf_size,
                                             MAX_PKT_BURST, sizeof(struct rte_pktmbuf_pool_private),
                                             rte_pktmbuf_pool_init, NULL,
                                             rte_pktmbuf_init, NULL, rte_socket_id(),
                                             MEMPOOL_F_SP_PUT | MEMPOOL_F_SC_GET);

Some experiments with various buf_sizes showed, that if I make the buffer large enough (e.g. pkt_bytes * 2) it seems to work at least for some NICs (with IXGBE driver).

DPDK: 20.11-rc1

Best regards,
Felix

                 reply	other threads:[~2020-10-27 13:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=AM0PR10MB19399D173D14868A0BC2306D89160@AM0PR10MB1939.EURPRD10.PROD.OUTLOOK.COM \
    --to=felix.moessbauer@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=henning.schild@siemens.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).