From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: RE: RFC - Tap io_uring PMD
Date: Wed, 6 Nov 2024 00:54:26 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F886@smartserver.smartshare.dk> (raw)
In-Reply-To: <20241105152556.2e5b8f91@hermes.local>
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Wednesday, 6 November 2024 00.26
>
> On Wed, 6 Nov 2024 00:22:19 +0100
> Morten Brørup <mb@smartsharesystems.com> wrote:
>
> > From what I understand, the TAP io_uring PMD only supports one RX
> queue per port and one TX queue per port (i.e. per TAP interface). We
> can take advantage of this:
>
>
> No kernel tap support multi queue and we need to use that.
Maybe I got it wrong then... I thought you said fanout (of kernel->TAP packets) would affect all fds associated with the TAP interface.
How can the application then use multiple queues?
Another thing is:
For which purposes do applications need multi queue support for TAP, considering the interface is for management traffic only?
If single queue suffices, it might make the PMD simpler.
On the other hand, it is more important making it simple for the application than making a simple PMD! :-)
next prev parent reply other threads:[~2024-11-05 23:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 21:56 Stephen Hemminger
2024-10-31 10:27 ` Morten Brørup
2024-11-01 0:34 ` Stephen Hemminger
2024-11-02 22:28 ` Morten Brørup
2024-11-05 18:58 ` Stephen Hemminger
2024-11-05 23:22 ` Morten Brørup
2024-11-05 23:25 ` Stephen Hemminger
2024-11-05 23:54 ` Morten Brørup [this message]
2024-11-06 0:52 ` Igor Gutorov
2024-11-07 16:30 ` Stephen Hemminger
2024-11-06 10:30 ` Konstantin Ananyev
2024-11-06 0:46 ` Varghese, Vipin
2024-11-06 7:46 ` Maxime Coquelin
2024-11-07 21:51 ` Morten Brørup
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=98CBD80474FA8B44BF855DF32C47DC35E9F886@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).