From: Jianhua Xie <jianhua.xie@freescale.com>
To: <roopa@cumulusnetworks.com>, <jiri@resnulli.us>,
<sfeldma@gmail.com>, <jhs@mojatatu.com>, <bcrl@kvack.org>,
<tgraf@suug.ch>, <john.fastabend@gmail.com>,
<stephen@networkplumber.org>, <linville@tuxdriver.com>,
<nhorman@tuxdriver.com>, <nicolas.dichtel@6wind.com>,
<vyasevic@redhat.com>, <f.fainelli@gmail.com>,
<buytenh@wantstofly.org>, <aviadr@mellanox.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<shm@cumulusnetworks.com>, <gospo@cumulusnetworks.com>,
Jianhua Xie <jianhua.xie@freescale.com>
Subject: Re: [PATCH 1/3] netdev: introduce new NETIF_F_HW_SWITCH_OFFLOAD feature flag for switch device offloads
Date: Fri, 5 Dec 2014 11:21:02 +0800 [thread overview]
Message-ID: <5481249E.7020902@freescale.com> (raw)
In-Reply-To: <1417746401-8140-2-git-send-email-roopa@cumulusnetworks.com>
在 2014年12月05日 10:26, roopa@cumulusnetworks.com 写道:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> This is a generic high level feature flag for all switch asic features today.
>
> switch drivers set this flag on switch ports. Logical devices like
> bridge, bonds, vxlans can inherit this flag from their slaves/ports.
>
> I had to use SWITCH in the name to avoid ambiguity with other feature
> flags. But, since i have been harping about not calling it 'switch',
> I am welcome to any suggestions :)
>
> An alternative to using a feature flag is to use a IFF_HW_OFFLOAD
> in net_device_flags.
> ---
> include/linux/netdev_features.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/netdev_features.h b/include/linux/netdev_features.h
> index 8e30685..68db1de 100644
> --- a/include/linux/netdev_features.h
> +++ b/include/linux/netdev_features.h
> @@ -66,6 +66,7 @@ enum {
> NETIF_F_HW_VLAN_STAG_FILTER_BIT,/* Receive filtering on VLAN STAGs */
> NETIF_F_HW_L2FW_DOFFLOAD_BIT, /* Allow L2 Forwarding in Hardware */
> NETIF_F_BUSY_POLL_BIT, /* Busy poll */
> + NETIF_F_HW_SWITCH_OFFLOAD_BIT, /* HW switch offload */
I am interested in this flag very much, but I am not very clear
how many offload capabilities does this flag imply. If this flag
belongs to a general flag and can be accepted by all vendors,
I will reuse this flag to introduce another out going data traffics
distribution offload method to bonding driver.
Thanks & B.R.
Jianhua
>
> /*
> * Add your fresh new feature above and remember to update
> @@ -124,6 +125,7 @@ enum {
> #define NETIF_F_HW_VLAN_STAG_TX __NETIF_F(HW_VLAN_STAG_TX)
> #define NETIF_F_HW_L2FW_DOFFLOAD __NETIF_F(HW_L2FW_DOFFLOAD)
> #define NETIF_F_BUSY_POLL __NETIF_F(BUSY_POLL)
> +#define NETIF_F_HW_SWITCH_OFFLOAD __NETIF_F(HW_SWITCH_OFFLOAD)
>
> /* Features valid for ethtool to change */
> /* = all defined minus driver/device-class-related */
next prev parent reply other threads:[~2014-12-05 3:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 2:26 [PATCH 1/3] netdev: introduce new NETIF_F_HW_SWITCH_OFFLOAD feature flag for switch device offloads roopa
2014-12-05 3:21 ` Jianhua Xie [this message]
2014-12-05 4:17 ` Roopa Prabhu
2014-12-05 4:43 ` Jianhua Xie
2014-12-05 6:08 ` Scott Feldman
2014-12-05 6:32 ` John Fastabend
2014-12-05 6:47 ` Scott Feldman
2014-12-05 7:41 ` Jiri Pirko
2014-12-05 14:16 ` Roopa Prabhu
2014-12-05 18:53 ` Scott Feldman
2014-12-05 19:07 ` Roopa Prabhu
2014-12-05 12:06 ` Jamal Hadi Salim
2014-12-05 12:17 ` Jiri Pirko
2014-12-05 12:50 ` Jamal Hadi Salim
2014-12-05 22:43 ` Thomas Graf
2014-12-06 7:46 ` Roopa Prabhu
2014-12-06 10:14 ` Thomas Graf
2014-12-06 18:59 ` Roopa Prabhu
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=5481249E.7020902@freescale.com \
--to=jianhua.xie@freescale.com \
--cc=aviadr@mellanox.com \
--cc=bcrl@kvack.org \
--cc=buytenh@wantstofly.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=gospo@cumulusnetworks.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=nicolas.dichtel@6wind.com \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=shm@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
--cc=tgraf@suug.ch \
--cc=vyasevic@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).