From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: "Björn Töpel" <bjorn.topel@gmail.com>,
"Gaul, Maximilian" <maximilian.gaul@hm.edu>
Cc: Xdp <xdp-newbies@vger.kernel.org>
Subject: Re: Shared Umem between processes
Date: Thu, 12 Mar 2020 12:00:56 +0100 [thread overview]
Message-ID: <87sgidon13.fsf@toke.dk> (raw)
In-Reply-To: <CAJ+HfNjNMhxzXTrwKjOZALO5=3UTgQz0ytyAMs5zoGB0HX29DA@mail.gmail.com>
Björn Töpel <bjorn.topel@gmail.com> writes:
> On Thu, 12 Mar 2020 at 10:17, Gaul, Maximilian <maximilian.gaul@hm.edu> wrote:
>>
> [...]
>>
>> Thank you so much Björn!
>>
>> just to wrap things up:
>>
>> - if I want to distribute packet processing from a single RX-Queue to
>> multiple sockets I have to use shared umem because it is not possible
>> to bind multiple af-xdp sockets onto the same RX-Queue
>
> Correct! And you need a tailored XDP program that spreads over the
> shared umem sockets!
Could we lift this restriction? Not with zero-copy, obviously, but if
there's a copy involved it seems it should be possible to support
several sockets on the same RXQ? That would make it possible to use XDP
as a per-CPU load balancer for a single RXQ, like we can do with cpumap
for packets hitting the stack today?
-Toke
next prev parent reply other threads:[~2020-03-12 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 15:58 Shared Umem between processes Gaul, Maximilian
2020-03-12 7:55 ` Björn Töpel
2020-03-12 8:20 ` AW: " Gaul, Maximilian
2020-03-12 8:38 ` Björn Töpel
2020-03-12 8:49 ` AW: " Gaul, Maximilian
2020-03-12 9:10 ` Björn Töpel
2020-03-12 9:17 ` AW: " Gaul, Maximilian
2020-03-12 9:40 ` Björn Töpel
2020-03-12 11:00 ` Toke Høiland-Jørgensen [this message]
2020-03-12 11:29 ` Björn Töpel
2020-03-12 15:48 ` AW: " Gaul, Maximilian
2020-03-15 15:29 ` Gaul, Maximilian
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=87sgidon13.fsf@toke.dk \
--to=toke@redhat.com \
--cc=bjorn.topel@gmail.com \
--cc=maximilian.gaul@hm.edu \
--cc=xdp-newbies@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.