From: David Ahern <dsahern@gmail.com>
To: Dmitry Safonov <dima@arista.com>, linux-kernel@vger.kernel.org
Cc: Alexander Duyck <alexander.h.duyck@linux.intel.com>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Ido Schimmel <idosch@mellanox.com>,
netdev@vger.kernel.org
Subject: Re: [RFC 4/4] net/ipv4/fib: Don't synchronise_rcu() every 512Kb
Date: Tue, 26 Mar 2019 11:57:42 -0600 [thread overview]
Message-ID: <dff0e80c-fa15-c28b-b34f-d80f59162051@gmail.com> (raw)
In-Reply-To: <bd638730-e23a-3d08-bd35-9c80af13692b@arista.com>
On 3/26/19 11:15 AM, Dmitry Safonov wrote:
> I still wonder if it's good to expose it to userspace rather than
> shrinker, but this probably should work for me - I'll test it in near days.
I did not know about the shrinker, so can not comment if it is better or
not. If so, my patch can always be reverted since it was just applied.
next prev parent reply other threads:[~2019-03-26 17:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 15:30 [RFC 0/4] net/fib: Speed up trie rebalancing for full view Dmitry Safonov
2019-03-26 15:30 ` [RFC 1/4] net/ipv4/fib: Remove run-time check in tnode_alloc() Dmitry Safonov
2019-04-01 15:40 ` Alexander Duyck
2019-04-01 15:55 ` Dmitry Safonov
2019-04-01 17:50 ` Alexander Duyck
2019-04-04 16:33 ` Dmitry Safonov
2019-03-26 15:30 ` [RFC 2/4] net/fib: Provide fib_balance_budget sysctl Dmitry Safonov
2019-04-01 18:09 ` Alexander Duyck
2019-04-04 18:31 ` Dmitry Safonov
2019-03-26 15:30 ` [RFC 3/4] net/fib: Check budget before should_{inflate,halve}() Dmitry Safonov
2019-04-01 18:20 ` Alexander Duyck
2019-03-26 15:30 ` [RFC 4/4] net/ipv4/fib: Don't synchronise_rcu() every 512Kb Dmitry Safonov
2019-03-26 15:39 ` David Ahern
2019-03-26 17:15 ` Dmitry Safonov
2019-03-26 17:57 ` David Ahern [this message]
2019-03-26 18:17 ` Dmitry Safonov
2019-03-26 23:14 ` Dmitry Safonov
2019-03-27 3:33 ` Paul E. McKenney
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=dff0e80c-fa15-c28b-b34f-d80f59162051@gmail.com \
--to=dsahern@gmail.com \
--cc=alexander.h.duyck@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dima@arista.com \
--cc=edumazet@google.com \
--cc=idosch@mellanox.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).