From: Simon Horman <horms@kernel.org>
To: edward.cree@amd.com
Cc: linux-net-drivers@amd.com, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com,
Edward Cree <ecree.xilinx@gmail.com>,
netdev@vger.kernel.org, habetsm.xilinx@gmail.com
Subject: Re: [PATCH net-next 0/7] sfc: basic conntrack offload
Date: Fri, 4 Aug 2023 15:44:26 +0200 [thread overview]
Message-ID: <ZM0AurjKOt8q0ezk@kernel.org> (raw)
In-Reply-To: <cover.1691063675.git.ecree.xilinx@gmail.com>
On Thu, Aug 03, 2023 at 12:56:16PM +0100, edward.cree@amd.com wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> Support offloading tracked connections and matching against them in
> TC chains on the PF and on representors.
> Later patch serieses will add NAT and conntrack-on-tunnel-netdevs;
> keep it simple for now.
Hi Ed,
I did provide a minr nit on patch 7/7, in response to that patch,
but overall this patchset looks good to me.
For the series,
Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2023-08-04 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 11:56 [PATCH net-next 0/7] sfc: basic conntrack offload edward.cree
2023-08-03 11:56 ` [PATCH net-next 1/7] sfc: add MAE table machinery for conntrack table edward.cree
2023-08-03 11:56 ` [PATCH net-next 2/7] sfc: functions to register for conntrack zone offload edward.cree
2023-08-03 11:56 ` [PATCH net-next 3/7] sfc: functions to insert/remove conntrack entries to MAE hardware edward.cree
2023-08-03 11:56 ` [PATCH net-next 4/7] sfc: offload conntrack flow entries (match only) from CT zones edward.cree
2023-08-03 11:56 ` [PATCH net-next 5/7] sfc: handle non-zero chain_index on TC rules edward.cree
2023-08-03 11:56 ` [PATCH net-next 6/7] sfc: conntrack state matches in " edward.cree
2023-08-03 11:56 ` [PATCH net-next 7/7] sfc: offload left-hand side rules for conntrack edward.cree
2023-08-04 13:43 ` Simon Horman
2023-08-07 13:12 ` Edward Cree
2023-08-07 14:44 ` Simon Horman
2023-08-04 13:44 ` Simon Horman [this message]
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=ZM0AurjKOt8q0ezk@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).