From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Marcus Wichelmann <marcus.wichelmann@hetzner-cloud.de>,
xdp-newbies@vger.kernel.org
Subject: Re: XDP packet queueing and scheduling capabilities
Date: Wed, 14 Feb 2024 17:21:32 +0100 [thread overview]
Message-ID: <877cj7dnjn.fsf@toke.dk> (raw)
In-Reply-To: <bcb43611-a463-4d1a-a6f6-dac340d571f8@hetzner-cloud.de>
Marcus Wichelmann <marcus.wichelmann@hetzner-cloud.de> writes:
> Am 13.02.24 um 14:03 schrieb Toke Høiland-Jørgensen:
>> What's your interest in this? I.e., what do you want to use them for?
>> Would be useful to know so I can make sure this is covered :)
>
> Hi, just wanting to let you know that we're also still very interested
> in this for our cloud-provider use case.
>
> We use XDP to route packets to and from VMs and want to also apply
> firewall rules on the way. For this, we need to buffer/delay reordered
> IP fragments that arrived before the first fragment until we have seen
> the required L4 header.
>
> Having a packet queue for this, like in your patch, that can also be
> dequeued again, would definitively be helpful for that.
>
> We'd also like to implement shaping in the future, so this is also very
> interesting for us.
Great, thanks for the feedback! Hadn't thought about frag reassembly,
but that should definitely be possible as well; will keep that in mind! :)
-Toke
next prev parent reply other threads:[~2024-02-14 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 4:27 XDP packet queueing and scheduling capabilities team lnx
2024-02-13 13:03 ` Toke Høiland-Jørgensen
2024-02-13 14:33 ` Alexandre Cassen
2024-02-13 15:01 ` Dave Taht
2024-02-13 16:07 ` Toke Høiland-Jørgensen
2024-02-13 17:31 ` Alexandre Cassen
2024-02-14 13:21 ` Toke Høiland-Jørgensen
2024-02-14 13:27 ` Marcus Wichelmann
2024-02-14 16:21 ` Toke Høiland-Jørgensen [this message]
2024-02-15 19:10 ` team lnx
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=877cj7dnjn.fsf@toke.dk \
--to=toke@redhat.com \
--cc=marcus.wichelmann@hetzner-cloud.de \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).