From: Dmitry Safonov <dima@arista.com>
To: David Ahern <dsahern@gmail.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 18:17:12 +0000 [thread overview]
Message-ID: <dbcd803c-3347-335e-bc5e-299c33f02b9f@arista.com> (raw)
In-Reply-To: <dff0e80c-fa15-c28b-b34f-d80f59162051@gmail.com>
On 3/26/19 5:57 PM, David Ahern wrote:
> 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.
Oh, don't misunderstand me - I didn't mean to say your patch is wrong,
but I wondered what made this preferable for you.
I've sent my patches as RFC, so probably - it's a place to discuss
what's better, rather than running, rushing and reverting you commit.
Initially, I was also thinking about introducing some sysctl like that,
but thought it's a bit "dirty" solution to expose it to userspace for
tuning, rather than make it work automatically in OOM.
On other side with your sysctl, there are some minor bits, those are
not-yet-perfect and asking to be improved if we go this way:
1. I've noticed that the limit is only being increased or set to zero.
Which in turn can result in more calls to synchronise rcu than
needed.
2. The memory summed up under the limit is only tnodes in tnode_free(),
while nodes are not summed there. Also some tnodes are being freed
with node_free(), if I'm not mistaken.
So please, don't take me wrong, your patch may also work for me, but
probably worth to discuss both ways and I very much value your opinion here.
Thanks,
Dmitry
next prev parent reply other threads:[~2019-03-26 18:17 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
2019-03-26 18:17 ` Dmitry Safonov [this message]
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=dbcd803c-3347-335e-bc5e-299c33f02b9f@arista.com \
--to=dima@arista.com \
--cc=alexander.h.duyck@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.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
all inboxes | Powered by JetHome®