From: Christopher Lameter <cl@linux.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH] slub: limit count of partial slabs scanned to gather statistics
Date: Fri, 8 May 2020 03:18:22 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2005080315290.56560@www.lameter.com> (raw)
In-Reply-To: <20200504125656.e3d04b350c807aba8a2a7271@linux-foundation.org>
On Mon, 4 May 2020, Andrew Morton wrote:
> But I guess it's better than nothing at all, unless there are
> alternative ideas?
I its highly unsusual to have such large partial lists. In a typical case
allocations whould reduce the size of the lists. 1000s? That is scary.
Are there inodes or dentries by chance?
The defrag stuff that I had been trying to do for a long time would solve
that issue but then objects would need to be made movable....
next prev parent reply other threads:[~2020-05-08 3:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 16:07 [PATCH] slub: limit count of partial slabs scanned to gather statistics Konstantin Khlebnikov
2020-05-04 19:56 ` Andrew Morton
2020-05-05 5:46 ` Konstantin Khlebnikov
2020-05-08 3:18 ` Christopher Lameter [this message]
2020-05-04 21:19 ` David Rientjes
2020-05-05 6:20 ` Konstantin Khlebnikov
2020-05-06 11:56 ` Vlastimil Babka
2020-05-07 5:25 ` Konstantin Khlebnikov
2020-05-07 14:12 ` Vlastimil Babka
2020-05-06 19:06 ` Qian Cai
2020-05-07 3:01 ` Qian Cai
2020-05-07 3:20 ` Stephen Rothwell
2020-05-07 5:15 ` Konstantin Khlebnikov
2020-05-07 18:24 ` David Rientjes
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=alpine.DEB.2.22.394.2005080315290.56560@www.lameter.com \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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).