From: Thomas Graf <tgraf@suug.ch>
To: roopa@cumulusnetworks.com
Cc: jiri@resnulli.us, sfeldma@gmail.com, jhs@mojatatu.com,
bcrl@kvack.org, 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,
netdev@vger.kernel.org, davem@davemloft.net,
shrijeet@cumulusnetworks.com, gospo@cumulusnetworks.com
Subject: Re: [RFC PATCH 4/4] bridge: make hw offload conditional on bridge and bridge port offload flags
Date: Fri, 21 Nov 2014 23:30:54 +0000 [thread overview]
Message-ID: <20141121233054.GB20810@casper.infradead.org> (raw)
In-Reply-To: <1416610170-21224-5-git-send-email-roopa@cumulusnetworks.com>
On 11/21/14 at 02:49pm, roopa@cumulusnetworks.com wrote:
> + nla_put_u8(skb, IFLA_BRPORT_GUARD,
> + br_get_port_flag(p, IFLA_BRPORT_GUARD, BR_BPDU_GUARD)) ||
A helper taking nla_put_br_flag(port, skb, attrtype, brflag) would simplify
this code a lot.
> @@ -305,7 +312,9 @@ static int br_set_port_state(struct net_bridge_port *p, u8 state)
>
> br_set_state(p, state);
> br_log_state(p);
> - netdev_sw_port_stp_update(p->dev, p->state);
> +
> + if (BR_HW_OFFLOAD(p->br))
> + netdev_sw_port_set_attr(p->dev, IFLA_BRPORT_STATE, &p->state);
I assume the yet unfinished netdev_sw_port_set_attr() will call
netdev_sw_port_stp_update()?
> @@ -316,13 +325,34 @@ static void br_set_port_flag(struct net_bridge_port *p, struct nlattr *tb[],
> {
> if (tb[attrtype]) {
> u8 flag = nla_get_u8(tb[attrtype]);
> - if (flag)
> - p->flags |= mask;
> - else
> + if (flag) {
> + flag_upper = flag & 0xf0
> + if (!flag_upper || (flag_upper & BRPORT_KERNEL))
> + p->flags |= mask;
> + if ((flag_upper & BRPORT_HW_OFFLOAD) ||
> + (BR_HW_OFFLOAD(p->br)))
> + /* Also set the port flag in hw */
> + netdev_sw_port_set_attr(p->dev, attrtype, 1);
I'm not sure I understand the || here. HW_OFFLOAD enabled on the
net_device is a conditional for all netdev_sw_port_set_attr() calls
and at the same time implies BRPORT_HW_OFFLOAD on all attributes.
As I read this code now, I don't see how you would offload individual
features to hardware.
> diff --git a/net/bridge/br_private.h b/net/bridge/br_private.h
> index 8f3f081..3ebd196 100644
> --- a/net/bridge/br_private.h
> +++ b/net/bridge/br_private.h
> @@ -41,6 +41,8 @@
> /* Path to usermode spanning tree program */
> #define BR_STP_PROG "/sbin/bridge-stp"
>
> +#define BR_HW_OFFLOAD(br) !!(br->dev->features & NETIF_F_HW_OFFLOAD)
Let's not add more non type safe macros. A static inline seems like
a better fit here.
next prev parent reply other threads:[~2014-11-21 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 22:49 [RFC PATCH 4/4] bridge: make hw offload conditional on bridge and bridge port offload flags roopa
2014-11-21 23:30 ` Thomas Graf [this message]
2014-11-22 0:33 ` 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=20141121233054.GB20810@casper.infradead.org \
--to=tgraf@suug.ch \
--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=shrijeet@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
--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