From: Jon Maloy <jmaloy@redhat.com>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>,
David Gibson <dgibson@redhat.com>,
Laurent Vivier <lvivier@redhat.com>
Subject: Performance with unified IPv4/IPv6 tap queues
Date: Thu, 10 Oct 2024 20:11:57 -0400 [thread overview]
Message-ID: <70acdd85-5dda-4bb1-b54c-e5e7d2f4d5ff@redhat.com> (raw)
Hi all,
I added the addressing/routing workarounds suggested by Stefano, and
the performance measurements now seems to be working flawlessly,
even the one Stefano said failed in his runs.
I made 5 runs from the master branch, and 5 with my two patches applied.
You can observe the resulta at
https://drive.google.com/drive/folders/1xGcWJ79smELbWOPwcJdsmyvoIrTz9R56
However, there seems to be a systematic decrease in throughput.
If we take the average over the runs for IPv6 ns - > host via tap,
we get 33.56 Gb/s vs 31.84 Gb/, i.e. a 5% difference.
I don´t really know what to make of this, and would like to know if
anybody else can confirm or falsify this.
///jon
next reply other threads:[~2024-10-11 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 0:11 Jon Maloy [this message]
2024-10-11 18:07 ` Performance with unified IPv4/IPv6 tap queues Stefano Brivio
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=70acdd85-5dda-4bb1-b54c-e5e7d2f4d5ff@redhat.com \
--to=jmaloy@redhat.com \
--cc=dgibson@redhat.com \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).