From: Florian Westphal <fw@strlen.de>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH RFC] netfilter: nf_tables: add flowtable map for xdp offload
Date: Mon, 23 Oct 2023 13:16:55 +0200 [thread overview]
Message-ID: <20231023111655.GA31012@breakpoint.cc> (raw)
In-Reply-To: <ZTZL3jpvunApjcTE@lore-desk>
Lorenzo Bianconi <lorenzo@kernel.org> wrote:
> thx for working on this, I tested this patch with the flowtable lookup kfunc
> I am working on (code is available here [0]) and it works properly.
Thanks!
> >
> > Do we need to support dev-in-multiple flowtables? I would like to
> > avoid this, this likely means the future "xdp" flag in nftables would
> > be restricted to "inet" family. Alternative would be to change the key to
> > 'device address plus protocol family', the xdp prog could derive that from the
> > packet data.
> >
> > Timeout handling. Should the XDP program even bother to refresh the
> > flowtable timeout?
>
> I was assuming the flowtable lookup kfunc can take care of it.
I'm worried about stale neigh cache, resp. making sure that it
gets renewed.
> > +struct nf_flowtable *nf_flowtable_by_dev(const struct net_device *dev)
> > +{
>
> I think this routine needs to be added to some include file (e.g.
> include/net/netfilter/nf_flow_table.h)
Right.
next prev parent reply other threads:[~2023-10-23 11:17 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 [this message]
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
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=20231023111655.GA31012@breakpoint.cc \
--to=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.