From: Simon Horman <simon.horman@corigine.com>
To: Subbaraya Sundeep <sbhatta@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, saeedm@nvidia.com, tariqt@nvidia.com,
roid@nvidia.com, leon@kernel.org, maxtram95@gmail.com,
kliteyn@nvidia.com, irusskikh@marvell.com, liorna@nvidia.com,
ehakim@nvidia.com, dbogdanov@marvell.com, sd@queasysnail.net,
sgoutham@marvell.com, gakula@marvell.com, naveenm@marvell.com,
hkelam@marvell.com, lcherian@marvell.com
Subject: Re: [net-next PATCH] macsec: Use helper macsec_netdev_priv for offload drivers
Date: Wed, 10 May 2023 12:29:43 +0200 [thread overview]
Message-ID: <ZFtyF3SqLCQleCZy@corigine.com> (raw)
In-Reply-To: <1683707289-2854-1-git-send-email-sbhatta@marvell.com>
On Wed, May 10, 2023 at 01:58:09PM +0530, Subbaraya Sundeep wrote:
> Now macsec on top of vlan can be offloaded to macsec offloading
> devices so that VLAN tag is sent in clear text on wire i.e,
> packet structure is DMAC|SMAC|VLAN|SECTAG. Offloading devices can
> simply enable NETIF_F_HW_MACSEC feature in netdev->vlan_features for
> this to work. But the logic in offloading drivers to retrieve the
> private structure from netdev needs to be changed to check whether
> the netdev received is real device or a vlan device and get private
> structure accordingly. This patch changes the offloading drivers to
> use helper macsec_netdev_priv instead of netdev_priv.
>
> Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-05-10 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 8:28 [net-next PATCH] macsec: Use helper macsec_netdev_priv for offload drivers Subbaraya Sundeep
2023-05-10 10:29 ` Simon Horman [this message]
2023-05-10 10:40 ` 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=ZFtyF3SqLCQleCZy@corigine.com \
--to=simon.horman@corigine.com \
--cc=davem@davemloft.net \
--cc=dbogdanov@marvell.com \
--cc=edumazet@google.com \
--cc=ehakim@nvidia.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=irusskikh@marvell.com \
--cc=kliteyn@nvidia.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liorna@nvidia.com \
--cc=maxtram95@gmail.com \
--cc=naveenm@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roid@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=sbhatta@marvell.com \
--cc=sd@queasysnail.net \
--cc=sgoutham@marvell.com \
--cc=tariqt@nvidia.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).