From: David Miller <davem@davemloft.net>
To: Jason@zx2c4.com
Cc: dcbw@redhat.com, stephen@networkplumber.org, netdev@vger.kernel.org
Subject: Re: To netlink or not to netlink, that is the question
Date: Thu, 12 Jan 2017 14:11:27 -0500 (EST) [thread overview]
Message-ID: <20170112.141127.426662758858102403.davem@davemloft.net> (raw)
In-Reply-To: <CAHmME9oYDdQGsQ8jQGJMeJ-0A6O+Och+Y+5Q_=Q=M9qgrxDq2Q@mail.gmail.com>
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
Date: Thu, 12 Jan 2017 20:02:14 +0100
> But what about fetching the list of all existing peers and ipmasks
> atomically? It seems like with multiple calls, if I'm using some kind
> of pagination, things could change in the process. That's why using
> one big buffer was most appealing... Any ideas about this?
This is a fact of life, dumps are always chopped into suitable
numbers of responses as necessary. We do this for IPV4 routes,
network interfaces, etc. and it all works out just fine.
The thing you should be asking yourself is, if something as heavily
used and fundamental as IPV4 can handle this, probably your scenerio
can be handled just fine as well.
next prev parent reply other threads:[~2017-01-12 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 13:01 To netlink or not to netlink, that is the question Jason A. Donenfeld
2017-01-12 17:14 ` Stephen Hemminger
2017-01-12 18:28 ` Jason A. Donenfeld
2017-01-12 18:43 ` Dan Williams
2017-01-12 19:02 ` Jason A. Donenfeld
2017-01-12 19:11 ` David Miller [this message]
2017-01-12 20:07 ` Jason A. Donenfeld
2017-01-12 20:27 ` David Miller
2017-01-13 7:17 ` Johannes Berg
2017-01-13 13:36 ` Nicolas Dichtel
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=20170112.141127.426662758858102403.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Jason@zx2c4.com \
--cc=dcbw@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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).