From: dennis.wagner@tuta.io
To: users@dpdk.org
Subject: [dpdk-users] DPDK layer 2 forwarding without modification / disable offloading
Date: Tue, 13 Jul 2021 13:29:21 +0200 (CEST) [thread overview]
Message-ID: <MeUcDWe--3-2@tuta.io> (raw)
Hello,
I am a student of computer science in Germany. Sorry, if this is a basic question.
I am trying to do some latency benchmarks with DPDK as a layer 2 relay. Here is what I did:
* my server is running Debian 10 and has 2 NICs Intel I210 Gigabit
* NICs are configured: dpdk-devbind.py --bind=uio_pci_generic 0000:02:00.0 / 0000:05:00.0
* examples/skeleton/basicfwd.c is used to relay traffic
* to measure the latency, traffic is recorded before and after the dpdk-box with tcpdump
* compare the 2 traces of a http download
I expected DPDK to pass all frames unmodified, but some frames after the handshake the traces start to diverge: the length of the frames change.
Could hardware offloading like TSO be the reason? How would I completely disable offloading?
Is this done in my DPDK application or with a tool like ethtool per interface?
Setting the offloads field in basicfwd.c (port_conf.txmode.offoads = 0; port_conf.rxmode.offoads = 0) did not work.
Thanks!
Dennis
reply other threads:[~2021-07-13 11:29 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=MeUcDWe--3-2@tuta.io \
--to=dennis.wagner@tuta.io \
--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).