From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Edward Cree <ecree@solarflare.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Conntrack offload questions
Date: Wed, 30 Oct 2019 09:38:29 +0100 [thread overview]
Message-ID: <20191030083829.toz5jucnfbqv5yz7@salvia> (raw)
In-Reply-To: <c191b305-e068-df82-aaee-d66b194d74f6@solarflare.com>
Hi Ed,
On Tue, Oct 29, 2019 at 06:02:57PM +0000, Edward Cree wrote:
> Hi Pablo,
>
> I've been trying to figure out how the kernel API is going to look for
> offloading conntrack entries into hardware (for ct_state matches in flower
> rules to match on), as we're developing some hardware that intends to
> support that. AFAICT such an API does not yet exist in nf-next.
>
> Back in 2017 you added some relevant-looking nf code [1] "Flow offload
> infrastructure", including an RFC patch [2] which you said you would "keep
> back until there's a driver". Is the API added in that patch (i.e.
> ndo_flow_offload()) still the current plan, or has the design changed at
> all over the course of the last two years?
>
> If you have some more up-to-date strawman/RFC code, that'd be really useful
> for me to develop a prototype against.
The most up to date code is available here:
https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf.git/log/?h=flow-offload-hw-v3
> I am assuming that the first actual upstream driver supporting conntrack
> offload will be something from Mellanox (they seem to have been driving
> this process) and that the offload API will be submitted along with that;
> is that assumption accurate?
I don't work for Mellanox, I have absolutely no idea what the plans
are. I received a few emails about how they might use the
infrastructure I made, to consolidate common infrastructure. So I'm
very much looking for to seeing patches like you are.
> The information contained in this message is confidential and is
> intended for the addressee(s) only. If you have received this
> message in error, please notify the sender immediately and delete
> the message. Unless you are an addressee (or authorized to receive
> for an addressee), you may not use, copy or disclose to anyone this
> message or any information contained in this message. The
> unauthorized use, disclosure, copying or alteration of this message
> is strictly prohibited.
Don't worry, I'll keep this confidential :-)
parent reply other threads:[~2019-10-30 8:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <c191b305-e068-df82-aaee-d66b194d74f6@solarflare.com>]
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=20191030083829.toz5jucnfbqv5yz7@salvia \
--to=pablo@netfilter.org \
--cc=ecree@solarflare.com \
--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 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).