From: "Toke Høiland-Jørgensen" <toke@kernel.org>
To: Pavel Vazharov <pavel@x3me.net>, netdev@vger.kernel.org
Subject: Re: Need of advice for XDP sockets on top of the interfaces behind a Linux bonding device
Date: Fri, 26 Jan 2024 20:28:27 +0100 [thread overview]
Message-ID: <87y1cb28tg.fsf@toke.dk> (raw)
In-Reply-To: <CAJEV1ijxNyPTwASJER1bcZzS9nMoZJqfR86nu_3jFFVXzZQ4NA@mail.gmail.com>
Pavel Vazharov <pavel@x3me.net> writes:
> 3. If the above scheme is supposed to work then is the bonding logic
> (LACP management traffic) affected by the access pattern of the XDP
> sockets? I mean, the order of Rx/Tx operations on the XDP sockets or
> something like that.
Well, it will be up to your application to ensure that it is not. The
XDP program will run before the stack sees the LACP management traffic,
so you will have to take some measure to ensure that any such management
traffic gets routed to the stack instead of to the DPDK application. My
immediate guess would be that this is the cause of those warnings?
-Toke
next prev parent reply other threads:[~2024-01-26 19:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 15:54 Need of advice for XDP sockets on top of the interfaces behind a Linux bonding device Pavel Vazharov
2024-01-26 19:28 ` Toke Høiland-Jørgensen [this message]
2024-01-27 3:58 ` Pavel Vazharov
2024-01-27 4:39 ` Jakub Kicinski
2024-01-27 5:08 ` Pavel Vazharov
[not found] ` <CAJEV1ij=K5Xi5LtpH7SHXLxve+JqMWhimdF50Ddy99G0E9dj_Q@mail.gmail.com>
2024-01-30 13:54 ` Pavel Vazharov
2024-01-30 14:32 ` Toke Høiland-Jørgensen
2024-01-30 14:40 ` Pavel Vazharov
2024-01-30 14:54 ` Toke Høiland-Jørgensen
2024-02-05 7:07 ` Magnus Karlsson
2024-02-07 15:49 ` Pavel Vazharov
2024-02-07 16:07 ` Pavel Vazharov
2024-02-07 19:00 ` Maciej Fijalkowski
2024-02-08 10:59 ` Pavel Vazharov
2024-02-08 15:47 ` Pavel Vazharov
2024-02-09 9:03 ` Pavel Vazharov
2024-02-09 18:37 ` Maciej Fijalkowski
2024-02-16 15:18 ` Maciej Fijalkowski
2024-02-16 17:24 ` Maciej Fijalkowski
2024-02-19 13:45 ` Pavel Vazharov
2024-02-19 14:56 ` Maciej Fijalkowski
2024-03-08 10:05 ` Pavel Vazharov
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=87y1cb28tg.fsf@toke.dk \
--to=toke@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@x3me.net \
/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).