From: Simon Horman <simon.horman@corigine.com>
To: edward.cree@amd.com
Cc: linux-net-drivers@amd.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com,
Edward Cree <ecree.xilinx@gmail.com>,
netdev@vger.kernel.org, habetsm.xilinx@gmail.com,
michal.swiatkowski@linux.intel.com
Subject: Re: [PATCH net-next v3 2/6] sfc: add notion of match on enc keys to MAE machinery
Date: Mon, 27 Mar 2023 16:27:32 +0200 [thread overview]
Message-ID: <ZCGn1PRIqti7/Ruv@corigine.com> (raw)
In-Reply-To: <6753bf9b0c144635dd5ed7ff3f26270d60ec8d73.1679912088.git.ecree.xilinx@gmail.com>
On Mon, Mar 27, 2023 at 11:36:04AM +0100, edward.cree@amd.com wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> Extend the MAE caps check to validate that the hardware supports these
> outer-header matches where used by the driver.
> Extend efx_mae_populate_match_criteria() to fill in the outer rule ID
> and VNI match fields.
> Nothing yet populates these match fields, nor creates outer rules.
>
> Signed-off-by: Edward Cree <ecree.xilinx@gmail.com>
> ---
> Changed in v3: adjusted description to clarify caps check
> Changed in v2: efx_mae_check_encap_match_caps now takes a `bool ipv6` rather
> than an `unsigned char ipv`, simplifying the code.
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-03-27 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 10:36 [PATCH net-next v3 0/6] sfc: support TC decap rules edward.cree
2023-03-27 10:36 ` [PATCH net-next v3 1/6] sfc: document TC-to-EF100-MAE action translation concepts edward.cree
2023-03-27 10:36 ` [PATCH net-next v3 2/6] sfc: add notion of match on enc keys to MAE machinery edward.cree
2023-03-27 14:27 ` Simon Horman [this message]
2023-03-27 10:36 ` [PATCH net-next v3 3/6] sfc: handle enc keys in efx_tc_flower_parse_match() edward.cree
2023-03-27 10:36 ` [PATCH net-next v3 4/6] sfc: add functions to insert encap matches into the MAE edward.cree
2023-03-27 14:28 ` Simon Horman
2023-03-27 10:36 ` [PATCH net-next v3 5/6] sfc: add code to register and unregister encap matches edward.cree
2023-03-27 14:28 ` Simon Horman
2023-03-27 10:36 ` [PATCH net-next v3 6/6] sfc: add offloading of 'foreign' TC (decap) rules edward.cree
2023-03-29 8:10 ` [PATCH net-next v3 0/6] sfc: support TC decap rules patchwork-bot+netdevbpf
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=ZCGn1PRIqti7/Ruv@corigine.com \
--to=simon.horman@corigine.com \
--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=michal.swiatkowski@linux.intel.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).