From: Andrew Lunn <andrew@lunn.ch>
To: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
Cc: ivecera@redhat.com, jiri@resnulli.us, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org,
sergey.matyukevich.os@quantenna.com, ashevchenko@quantenna.com,
smaksimenko@quantenna.com, dlebed@quantenna.com
Subject: Re: [Bridge] [PATCH net-next 1/5] bridge: initialize port flags with switchdev defaults
Date: Sat, 10 Mar 2018 17:30:50 +0100 [thread overview]
Message-ID: <20180310163050.GF29174@lunn.ch> (raw)
In-Reply-To: <20180310030308.12947-2-igor.mitsyanko.os@quantenna.com>
On Fri, Mar 09, 2018 at 07:03:04PM -0800, Igor Mitsyanko wrote:
> Default bridge port flags for switchdev devices can be different from
> what is used in bridging core. Get default value from switchdev itself
> on port initialization.
>
> Signed-off-by: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
> ---
> net/bridge/br_if.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/net/bridge/br_if.c b/net/bridge/br_if.c
> index 9ba4ed6..d658b55 100644
> --- a/net/bridge/br_if.c
> +++ b/net/bridge/br_if.c
> @@ -342,6 +342,21 @@ static int find_portno(struct net_bridge *br)
> return (index >= BR_MAX_PORTS) ? -EXFULL : index;
> }
>
> +static unsigned long nbp_flags_get_default(struct net_device *dev)
> +{
> + struct switchdev_attr attr = {
> + .orig_dev = dev,
> + .id = SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS,
> + };
> + int ret;
> +
> + ret = switchdev_port_attr_get(dev, &attr);
> + if (ret)
> + return BR_LEARNING | BR_FLOOD | BR_MCAST_FLOOD | BR_BCAST_FLOOD;
Hi Igor
Please check if ret == -EOPNOTSUPP and only then use the defaults. A
real error should be propagated, causing new_nbp to fail. You might
also consider what to do when ENODATA is returned.
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
Cc: ivecera@redhat.com, jiri@resnulli.us, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org,
sergey.matyukevich.os@quantenna.com, ashevchenko@quantenna.com,
smaksimenko@quantenna.com, dlebed@quantenna.com
Subject: Re: [PATCH net-next 1/5] bridge: initialize port flags with switchdev defaults
Date: Sat, 10 Mar 2018 17:30:50 +0100 [thread overview]
Message-ID: <20180310163050.GF29174@lunn.ch> (raw)
In-Reply-To: <20180310030308.12947-2-igor.mitsyanko.os@quantenna.com>
On Fri, Mar 09, 2018 at 07:03:04PM -0800, Igor Mitsyanko wrote:
> Default bridge port flags for switchdev devices can be different from
> what is used in bridging core. Get default value from switchdev itself
> on port initialization.
>
> Signed-off-by: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
> ---
> net/bridge/br_if.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/net/bridge/br_if.c b/net/bridge/br_if.c
> index 9ba4ed6..d658b55 100644
> --- a/net/bridge/br_if.c
> +++ b/net/bridge/br_if.c
> @@ -342,6 +342,21 @@ static int find_portno(struct net_bridge *br)
> return (index >= BR_MAX_PORTS) ? -EXFULL : index;
> }
>
> +static unsigned long nbp_flags_get_default(struct net_device *dev)
> +{
> + struct switchdev_attr attr = {
> + .orig_dev = dev,
> + .id = SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS,
> + };
> + int ret;
> +
> + ret = switchdev_port_attr_get(dev, &attr);
> + if (ret)
> + return BR_LEARNING | BR_FLOOD | BR_MCAST_FLOOD | BR_BCAST_FLOOD;
Hi Igor
Please check if ret == -EOPNOTSUPP and only then use the defaults. A
real error should be propagated, causing new_nbp to fail. You might
also consider what to do when ENODATA is returned.
Andrew
next prev parent reply other threads:[~2018-03-10 16:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 3:03 [Bridge] [PATCH net-next 0/5] Switchdev: flooding offload option Igor Mitsyanko
2018-03-10 3:03 ` Igor Mitsyanko
2018-03-10 3:03 ` [Bridge] [PATCH net-next 1/5] bridge: initialize port flags with switchdev defaults Igor Mitsyanko
2018-03-10 3:03 ` Igor Mitsyanko
2018-03-10 16:30 ` Andrew Lunn [this message]
2018-03-10 16:30 ` Andrew Lunn
2018-03-12 18:44 ` [Bridge] " Igor Mitsyanko
2018-03-12 18:44 ` Igor Mitsyanko
2018-03-10 16:32 ` [Bridge] " Stephen Hemminger
2018-03-10 16:32 ` Stephen Hemminger
2018-03-12 19:03 ` [Bridge] " Igor Mitsyanko
2018-03-12 19:03 ` Igor Mitsyanko
2018-03-10 3:03 ` [Bridge] [PATCH net-next 2/5] bridge: propagate BR_ flags updates through sysfs to switchdev Igor Mitsyanko
2018-03-10 3:03 ` Igor Mitsyanko
2018-03-10 16:38 ` [Bridge] " Andrew Lunn
2018-03-10 16:38 ` Andrew Lunn
2018-03-12 20:07 ` [Bridge] " Igor Mitsyanko
2018-03-12 20:07 ` Igor Mitsyanko
2018-03-10 3:03 ` [Bridge] [RFC PATCH net-next 3/5] bridge: allow switchdev port to handle flooding by itself Igor Mitsyanko
2018-03-10 3:03 ` Igor Mitsyanko
2018-03-10 16:55 ` [Bridge] " Andrew Lunn
2018-03-10 16:55 ` Andrew Lunn
2018-03-12 23:00 ` [Bridge] " Igor Mitsyanko
2018-03-12 23:00 ` Igor Mitsyanko
2018-03-13 1:11 ` [Bridge] " Andrew Lunn
2018-03-13 1:11 ` Andrew Lunn
2018-03-13 14:41 ` [Bridge] " Roopa Prabhu
2018-03-13 14:41 ` Roopa Prabhu
2018-03-10 3:03 ` [Bridge] [RFC PATCH net-next 4/5] bridge: provide sysfs and netlink interface to set BR_FLOOD_OFFLOAD Igor Mitsyanko
2018-03-10 3:03 ` Igor Mitsyanko
2018-03-10 3:03 ` [Bridge] [RFC PATCH net-next 5/5] bridge: verify "HW only" flags can't be set without HW support Igor Mitsyanko
2018-03-10 3:03 ` Igor Mitsyanko
2018-03-10 22:08 ` [Bridge] [PATCH net-next 0/5] Switchdev: flooding offload option Andrew Lunn
2018-03-10 22:08 ` Andrew Lunn
2018-03-12 23:08 ` [Bridge] " Igor Mitsyanko
2018-03-12 23:08 ` Igor Mitsyanko
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=20180310163050.GF29174@lunn.ch \
--to=andrew@lunn.ch \
--cc=ashevchenko@quantenna.com \
--cc=bridge@lists.linux-foundation.org \
--cc=dlebed@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=sergey.matyukevich.os@quantenna.com \
--cc=smaksimenko@quantenna.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.