From: Andrew Morton <akpm@linux-foundation.org>
To: Kirill Tkhai <ktkhai@virtuozzo.com>
Cc: vdavydov.dev@gmail.com, mhocko@suse.com, aryabinin@virtuozzo.com,
ying.huang@intel.com, penguin-kernel@I-love.SAKURA.ne.jp,
willy@infradead.org, shakeelb@google.com, jbacik@fb.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Use special value SHRINKER_REGISTERING instead list_empty() check
Date: Fri, 3 Aug 2018 15:51:20 -0700 [thread overview]
Message-ID: <20180803155120.0d65511b46c100565b4f8a2c@linux-foundation.org> (raw)
In-Reply-To: <153331055842.22632.9290331685041037871.stgit@localhost.localdomain>
On Fri, 03 Aug 2018 18:36:14 +0300 Kirill Tkhai <ktkhai@virtuozzo.com> wrote:
> The patch introduces a special value SHRINKER_REGISTERING to use instead
> of list_empty() to detect a semi-registered shrinker.
>
> This should be clearer for a reader since "list is empty" is not
> an intuitive state of a shrinker), and this gives a better assembler
> code:
>
> Before:
> callq <idr_find>
> mov %rax,%r15
> test %rax,%rax
> je <shrink_slab_memcg+0x1d5>
> mov 0x20(%rax),%rax
> lea 0x20(%r15),%rdx
> cmp %rax,%rdx
> je <shrink_slab_memcg+0xbd>
> mov 0x8(%rsp),%edx
> mov %r15,%rsi
> lea 0x10(%rsp),%rdi
> callq <do_shrink_slab>
>
> After:
> callq <idr_find>
> mov %rax,%r15
> lea -0x1(%rax),%rax
> cmp $0xfffffffffffffffd,%rax
> ja <shrink_slab_memcg+0x1cd>
> mov 0x8(%rsp),%edx
> mov %r15,%rsi
> lea 0x10(%rsp),%rdi
> callq ffffffff810cefd0 <do_shrink_slab>
>
> Also, improve the comment.
All this isn't terribly nice. Why can't we avoid installing the
shrinker into the idr until it is fully initialized?
Or extend the down_write(shrinker_rwsem) coverage so it protects the
entire initialization, instead of only in the prealloc_memcg_shrinker()
part of that initialization. This is not as good - it would be better
to do all the initialization locklessly then just install the fully
initialized thing under the lock.
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -170,6 +170,21 @@ static LIST_HEAD(shrinker_list);
> static DECLARE_RWSEM(shrinker_rwsem);
>
> #ifdef CONFIG_MEMCG_KMEM
> +
> +/*
> + * There is a window between prealloc_shrinker()
> + * and register_shrinker_prepared(). We don't want
> + * to clear bit of a shrinker in such the state
> + * in shrink_slab_memcg(), since this will impose
> + * restrictions on a code registering a shrinker
> + * (they would have to guarantee, their LRU lists
> + * are empty till shrinker is completely registered).
> + * So, we use this value to detect the situation,
> + * when id is assigned, but shrinker is not completely
> + * registered yet.
> + */
This comment is still quite hard to understand. Could you please spend
a little more time over it?
next prev parent reply other threads:[~2018-08-03 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 15:36 Kirill Tkhai
2018-08-03 22:51 ` Andrew Morton [this message]
2018-08-03 23:03 ` Matthew Wilcox
2018-08-04 18:42 ` Kirill Tkhai
2018-08-05 0:03 ` Matthew Wilcox
2018-08-05 5:30 ` Kirill Tkhai
2018-08-05 12:50 ` Matthew Wilcox
2018-08-06 8:55 ` Kirill Tkhai
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=20180803155120.0d65511b46c100565b4f8a2c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=jbacik@fb.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=shakeelb@google.com \
--cc=vdavydov.dev@gmail.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.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