From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, idosch@mellanox.com,
eladr@mellanox.com, yotamg@mellanox.com, nogahf@mellanox.com,
arkadis@mellanox.com, ogerlitz@mellanox.com,
roopa@cumulusnetworks.com, dsa@cumulusnetworks.com,
nikolay@cumulusnetworks.com, andy@greyhouse.net,
vivien.didelot@savoirfairelinux.com, andrew@lunn.ch,
f.fainelli@gmail.com, alexander.h.duyck@intel.com,
kaber@trash.net
Subject: Re: [patch net-next v2 10/11] mlxsw: spectrum_router: Request a dump of FIB tables during init
Date: Wed, 23 Nov 2016 18:08:23 +0100 [thread overview]
Message-ID: <1479920903.4037682.797206209.599A8C7A@webmail.messagingengine.com> (raw)
In-Reply-To: <20161123170436.GC1873@nanopsycho>
On Wed, Nov 23, 2016, at 18:04, Jiri Pirko wrote:
> >Sure, but an abort function can be provided to the kernel anyway and the
> >driver can care about that.
>
> Ok, how?
I think just a sysctl ontop of this series is enough plus a pr_warn.
Rocker and mlxsw are responsible to loop for a maximum amount of time.
Otherwise, if more fancy, can we provide an
fib_inconsistency_notification function pointer in netdev_ops?
Bye and thanks,
Hannes
next prev parent reply other threads:[~2016-11-23 17:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 14:34 [patch net-next v2 00/11] ipv4: fib: Allow modules to dump FIB tables Jiri Pirko
2016-11-23 14:34 ` [patch net-next v2 01/11] ipv4: fib: Export free_fib_info() Jiri Pirko
2016-11-23 14:34 ` [patch net-next v2 02/11] ipv4: fib: Add fib_info_hold() helper Jiri Pirko
2016-11-23 14:34 ` [patch net-next v2 03/11] mlxsw: core: Create an ordered workqueue for FIB offload Jiri Pirko
2016-11-23 14:34 ` [patch net-next v2 04/11] mlxsw: spectrum_router: Implement FIB offload in deferred work Jiri Pirko
2016-11-23 14:34 ` [patch net-next v2 05/11] rocker: Create an ordered workqueue for FIB offload Jiri Pirko
2016-11-23 14:34 ` [patch net-next v2 06/11] rocker: Implement FIB offload in deferred work Jiri Pirko
2016-11-23 14:34 ` [patch net-next v2 07/11] ipv4: fib: Convert FIB notification chain to be atomic Jiri Pirko
2016-11-23 14:34 ` [patch net-next v2 08/11] ipv4: fib: Allow for consistent FIB dumping Jiri Pirko
2016-11-23 14:34 ` [patch net-next v2 09/11] ipv4: fib: Add an API to request a FIB dump Jiri Pirko
2016-11-23 17:47 ` Hannes Frederic Sowa
2016-11-23 19:53 ` Ido Schimmel
2016-11-23 23:04 ` Hannes Frederic Sowa
2016-11-24 8:47 ` Ido Schimmel
2016-11-24 12:34 ` Hannes Frederic Sowa
2016-11-23 14:48 ` [patch net-next v2 10/11] mlxsw: spectrum_router: Request a dump of FIB tables during init Jiri Pirko
2016-11-23 16:00 ` Hannes Frederic Sowa
2016-11-23 16:04 ` Jiri Pirko
2016-11-23 16:59 ` Hannes Frederic Sowa
2016-11-23 17:04 ` Jiri Pirko
2016-11-23 17:08 ` Hannes Frederic Sowa [this message]
2016-11-23 19:22 ` Ido Schimmel
2016-11-23 19:45 ` Jiri Pirko
2016-11-23 14:48 ` [patch net-next v2 11/11] rocker: Register FIB notifier before creating ports Jiri Pirko
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=1479920903.4037682.797206209.599A8C7A@webmail.messagingengine.com \
--to=hannes@stressinduktion.org \
--cc=alexander.h.duyck@intel.com \
--cc=andrew@lunn.ch \
--cc=andy@greyhouse.net \
--cc=arkadis@mellanox.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=eladr@mellanox.com \
--cc=f.fainelli@gmail.com \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=nogahf@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=roopa@cumulusnetworks.com \
--cc=vivien.didelot@savoirfairelinux.com \
--cc=yotamg@mellanox.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).