From: Andrew Lunn <andrew@lunn.ch>
To: Ido Schimmel <idosch@idosch.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, davem@davemloft.net,
vivien.didelot@savoirfairelinux.com, jiri@resnulli.us
Subject: Re: [PATCH net-next 0/4] net: switchdev: Avoid sleep in atomic with DSA
Date: Mon, 9 Jan 2017 22:23:20 +0100 [thread overview]
Message-ID: <20170109212320.GB20958@lunn.ch> (raw)
In-Reply-To: <20170109211436.GB28310@splinter>
> Truth be told, I don't quite understand why switchdev infra even tries
> to dump the VLANs from the device. Like, in which situations is this
> going to be different from what the software bridge reports?
What happens when the hardware is out of resources and says sorry,
cannot do that. There has been a few discussions about what to do in
that situation. Fall back to software, i.e. the software bridge does
it, or totally fail the operation. If you are failing back to
software, the states can be different.
Andrew
next prev parent reply other threads:[~2017-01-09 21:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 19:44 [PATCH net-next 0/4] net: switchdev: Avoid sleep in atomic with DSA Florian Fainelli
2017-01-09 19:45 ` [PATCH net-next 1/4] net: switchdev: Prepare for deferred functions modifying objects Florian Fainelli
2017-01-09 19:45 ` [PATCH net-next 2/4] net: switchdev: Add object dump deferred operation Florian Fainelli
2017-01-09 19:45 ` [PATCH net-next 3/4] net: switchdev: Add switchdev_port_bridge_getlink_deferred Florian Fainelli
2017-01-09 20:11 ` Marcelo Ricardo Leitner
2017-01-09 20:13 ` Florian Fainelli
2017-01-09 20:28 ` Marcelo Ricardo Leitner
2017-01-09 20:29 ` Florian Fainelli
2017-01-10 0:25 ` kbuild test robot
2017-01-09 19:45 ` [PATCH net-next 4/4] net: dsa: Utilize switchdev_port_bridge_getlink_deferred() Florian Fainelli
2017-01-09 20:48 ` [PATCH net-next 0/4] net: switchdev: Avoid sleep in atomic with DSA Ido Schimmel
2017-01-09 20:56 ` Florian Fainelli
2017-01-09 21:14 ` Ido Schimmel
2017-01-09 21:23 ` Andrew Lunn [this message]
2017-01-09 21:29 ` Ido Schimmel
2017-01-10 12:08 ` Jiri Pirko
2017-01-10 13:25 ` Ido Schimmel
2017-01-10 14:18 ` Jiri Pirko
2017-01-10 16:08 ` Ido Schimmel
2017-01-10 16:13 ` Jiri Pirko
2017-01-11 1:42 ` Florian Fainelli
2017-01-11 14:59 ` Andrew Lunn
2017-01-09 21:19 ` Vivien Didelot
2017-01-11 1:26 ` David Miller
2017-01-09 21:05 ` Andrew Lunn
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=20170109212320.GB20958@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=idosch@idosch.org \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).