From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: jiri@resnulli.us, netdev@vger.kernel.org, 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,
kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net
Subject: Re: [patch net-next 6/8] ipv4: fib: Add an API to request a FIB dump
Date: Wed, 16 Nov 2016 11:27:35 -0500 (EST) [thread overview]
Message-ID: <20161116.112735.19078311822311561.davem@davemloft.net> (raw)
In-Reply-To: <e795e6e0-a680-a2c3-7d5e-afd966104a4a@stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Wed, 16 Nov 2016 15:51:01 +0100
> I don't see a way around doing a journal like in filesystems somehow,
We really just need a sequence counter incremented for each insert/remove,
and restart the dump from the beginning if it changes mid-dump.
next prev parent reply other threads:[~2016-11-16 16:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 14:08 [patch net-next 0/8] ipv4: fib: Allow modules to dump FIB tables Jiri Pirko
2016-11-16 14:08 ` [patch net-next 1/8] ipv4: fib: Export free_fib_info() Jiri Pirko
2016-11-16 14:08 ` [patch net-next 2/8] mlxsw: spectrum_router: Implement FIB offload in delayed work Jiri Pirko
2016-11-16 14:08 ` [patch net-next 3/8] rocker: " Jiri Pirko
2016-11-16 14:08 ` [patch net-next 4/8] ipv4: fib: Convert FIB notification chain to be atomic Jiri Pirko
2016-11-16 14:09 ` [patch net-next 5/8] net: ipv4: Send notifications only after removing FIB alias Jiri Pirko
2016-11-16 14:09 ` [patch net-next 6/8] ipv4: fib: Add an API to request a FIB dump Jiri Pirko
2016-11-16 14:51 ` Hannes Frederic Sowa
2016-11-16 15:18 ` Ido Schimmel
2016-11-16 17:35 ` Hannes Frederic Sowa
2016-11-16 18:51 ` Ido Schimmel
2016-11-16 19:43 ` Hannes Frederic Sowa
2016-11-16 21:06 ` Ido Schimmel
2016-11-17 13:10 ` Ido Schimmel
2016-11-17 14:36 ` Hannes Frederic Sowa
2016-11-17 16:45 ` David Miller
2016-11-17 17:20 ` Hannes Frederic Sowa
2016-11-17 18:16 ` David Miller
2016-11-17 19:03 ` Hannes Frederic Sowa
2016-11-17 18:32 ` Ido Schimmel
2016-11-17 19:05 ` Hannes Frederic Sowa
2016-11-16 16:27 ` David Miller [this message]
2016-11-16 16:42 ` Ido Schimmel
2016-11-16 16:56 ` Hannes Frederic Sowa
2016-11-16 14:09 ` [patch net-next 7/8] mlxsw: spectrum_router: Request a dump of FIB tables during init Jiri Pirko
2016-11-16 14:09 ` [patch net-next 8/8] rocker: " Jiri Pirko
2016-11-16 16:38 ` [patch net-next 0/8] ipv4: fib: Allow modules to dump FIB tables Alexander Duyck
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=20161116.112735.19078311822311561.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.h.duyck@intel.com \
--cc=andrew@lunn.ch \
--cc=andy@greyhouse.net \
--cc=arkadis@mellanox.com \
--cc=dsa@cumulusnetworks.com \
--cc=eladr@mellanox.com \
--cc=f.fainelli@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--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=yoshfuji@linux-ipv6.org \
--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).