From: Julien Plante <julien.plante@obspm.fr>
To: users@dpdk.org
Subject: Jumbo Frames on Memif PMD
Date: Thu, 12 May 2022 14:41:57 +0200 [thread overview]
Message-ID: <81c0f2aa-a469-0e1c-a9f6-d4762dad92e8@obspm.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
Hi,
I'm trying to use the memif PMD with Jumbo Frames, without any success yet.
Please note that I'm currently using DPDK 21.11, but could consider
updating.
On standard packet size, I'm able to transmit packets using memif with
the following commands:
Terminal 1 (receiver, launch first):
# ./dpdk-testpmd -l 2-3 --vdev=net_memif0,id=0,role=server
--file-prefix=pmd1 -- --forward-mode=rxonly --max-pkt-len=1518
Terminal 2 (sender, launch second):
# ./dpdk-testpmd -l 0-1 --vdev=net_memif0,id=0,role=client
--file-prefix=pmd2 -- --forward-mode=txonly --max-pkt-len=1518
When trying to send Jumbo Frames, I get an error on the server launch:
# ./dpdk-testpmd -l 2-3 --vdev=net_memif0,id=0,role=server
--file-prefix=pmd1 -- --forward-mode=rxonly --max-pkt-len=9000
...
Frame size (9000) > device max frame size (1518) for port_id 0
...
Do you know if it is possible to increase this device max frame size for
the memif PMD ?
About what I tried:
- Changing the bsize (Size of single packet buffer) option of the PMD to
a value higher than 9000 (I tried 9000 and 2^14=16384).
I did not understand what this parameter changes, but it did not seem
to help, the error stayed the same.
- Reading the doc (both DPDK
<https://doc.dpdk.org/guides/nics/memif.html>'s and VPP
<https://docs.fd.io/vpp/17.10/libmemif_doc.html>'s), searching for MTU
limitations, but saw no such thing.
- Start from the error message to find where the device max frame size
is set. It is initialized at drivers/net/memif/rte_eth_memif.c:198,
to the value RTE_ETHER_MAX_LEN (1518), and left untouched after that.
Is there any reason to limit the PMD to this value, or we could
add a setter for this value ?
Thanks for any help on this issue,
Julien
[-- Attachment #2: Type: text/html, Size: 2454 bytes --]
next reply other threads:[~2022-05-16 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 12:41 Julien Plante [this message]
[not found] ` <CGME20220516073835epcas1p12e29aed41f29e7022be13c256d646ae2@epcms1p6>
2022-05-17 4:38 ` 김문정
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=81c0f2aa-a469-0e1c-a9f6-d4762dad92e8@obspm.fr \
--to=julien.plante@obspm.fr \
--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).