From: "Toke Høiland-Jørgensen" <toke@kernel.org>
To: Florian Westphal <fw@strlen.de>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org,
Lorenzo Bianconi <lorenzo@kernel.org>
Subject: Re: [PATCH RFC] netfilter: nf_tables: add flowtable map for xdp offload
Date: Thu, 02 Nov 2023 12:07:31 +0100 [thread overview]
Message-ID: <87fs1o1ki4.fsf@toke.dk> (raw)
In-Reply-To: <20231102105434.GF6174@breakpoint.cc>
Florian Westphal <fw@strlen.de> writes:
> Toke Høiland-Jørgensen <toke@kernel.org> wrote:
>> > It might make more sense to intentionally have packets
>> > flow through the normal path periodically so neigh entries are up to
>> > date.
>>
>> Hmm, I see what you mean, but I worry that this would lead to some nasty
>> latency blips when a flow transitions back and forth between kernel and
>> XDP paths. Also, there's a reordering problem as the state is changed:
>> the first goes through the stack, sets the flow state to active, then
>> gets transmitted. But while that sits in the qdisc waiting to go out on
>> the wire, the next packet arrives, gets handled by the XDP fastpath and
>> ends up overtaking the first packet on the TX side. Not sure we have a
>> good solution for this in general :(
>
> From nft based flowtable offload we already had a feature request to
> bounce flows back to normal path periodially, this was because people
> wanted to make sure that long-living flows get revalidated vs. current
> netfilter ruleset and not the one that was active at flow offload time.
>
> There was a patch for it, using a new sysctl, and author never came
> back with an updated patch to handle this via the ruleset instead.
Right, if there's an existing policy knob for this it makes sense to
support it in the XDP case as well, of course.
Does HW flow offload deal with that reordering case at all, BTW? I
assume it could happen for that as well?
-Toke
next prev parent reply other threads:[~2023-11-02 11:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 20:25 [PATCH RFC] netfilter: nf_tables: add flowtable map for xdp offload Florian Westphal
2023-10-23 10:33 ` Lorenzo Bianconi
2023-10-23 11:16 ` Florian Westphal
2023-11-02 8:30 ` Florian Westphal
2023-11-09 11:09 ` Florian Westphal
2023-11-02 10:49 ` Toke Høiland-Jørgensen
2023-11-02 10:54 ` Florian Westphal
2023-11-02 11:07 ` Toke Høiland-Jørgensen [this message]
2023-11-02 11:11 ` Florian Westphal
2023-11-02 11:07 ` Florian Westphal
2023-11-02 11:25 ` Toke Høiland-Jørgensen
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=87fs1o1ki4.fsf@toke.dk \
--to=toke@kernel.org \
--cc=fw@strlen.de \
--cc=lorenzo@kernel.org \
--cc=netfilter-devel@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.