From: Vladimir Davydov <vdavydov@virtuozzo.com>
To: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] slub: reap free slabs periodically
Date: Tue, 14 Jun 2016 11:13:12 +0300 [thread overview]
Message-ID: <20160614081312.GL30465@esperanza> (raw)
In-Reply-To: <alpine.DEB.2.20.1606101629520.6786@east.gentwo.org>
On Fri, Jun 10, 2016 at 04:32:26PM -0500, Christoph Lameter wrote:
> One reason for SLUBs creation was the 2 second scans in SLAB which causes
> significant disruption of latency sensitive tasksk.
That's not good, indeed.
>
> You can simply implement a reaper in userspace by running
>
> slabinfo -s
>
> if you have to have this.
Doing this periodically would probably hurt performance of active caches
as 'slabinfo -s' shrinks all slabs unconditionally, even if they are
being actively used. OTOH, one could trigger shrinking slabs only on
memory pressure. That would require yet another daemon tracking the
system state, but it is doable I guess.
Thanks a lot for your input, Christoph.
>
> There is no need to duplicate SLAB problems.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-06-14 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 16:14 [PATCH RFC] slub: reap free slabs periodically Vladimir Davydov
2016-06-10 21:32 ` Christoph Lameter
2016-06-14 8:13 ` Vladimir Davydov [this message]
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=20160614081312.GL30465@esperanza \
--to=vdavydov@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--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).