From: Christoph Lameter <cl@gentwo.org>
To: Roman Gushchin <klamm@yandex-team.ru>
Cc: Pekka Enberg <penberg@kernel.org>,
mpm@selenic.com, akpm@linux-foundation.org, mgorman@suse.de,
David Rientjes <rientjes@google.com>,
glommer@gmail.com, hannes@cmpxchg.org, minchan@kernel.org,
jiang.liu@huawei.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slub: Avoid direct compaction if possible
Date: Fri, 14 Jun 2013 16:08:02 +0000 [thread overview]
Message-ID: <0000013f43718d4d-7bb260e7-8115-4891-bb26-6febacb7169d-000000@email.amazonses.com> (raw)
In-Reply-To: <51BB33FE.1020403@yandex-team.ru>
On Fri, 14 Jun 2013, Roman Gushchin wrote:
> But there is an actual problem, that this patch solves.
> Sometimes I saw the following issue on some machines:
> all CPUs are performing compaction, system time is about 80%,
> system is completely unreliable. It occurs only on machines
> with specific workload (distributed data storage system, so,
> intensive disk i/o is performed). A system can fall into
> this state fast and unexpectedly or by progressive degradation.
Well that is not a slab allocator specific issue but related to compaction
concurrency. Likely cache line contention is causing a severe slowday. But
that issue could be triggered by any subsystem that does lots of memory
allocations. I would suggest that we try to address the problem in the
compaction logic rather than modifying allocators.
Mel?
--
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>
next prev parent reply other threads:[~2013-06-14 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 13:17 Roman Gushchin
2013-06-14 14:32 ` Christoph Lameter
2013-06-14 15:17 ` Roman Gushchin
2013-06-14 16:08 ` Christoph Lameter [this message]
2013-06-14 16:52 ` Roman Gushchin
2013-06-14 20:26 ` David Rientjes
2013-06-17 12:34 ` Roman Gushchin
2013-06-17 14:27 ` Michal Hocko
2013-06-17 14:54 ` Roman Gushchin
2013-06-17 21:44 ` David Rientjes
2013-06-27 8:49 ` Roman Gushchin
2013-06-27 20:41 ` David Rientjes
2013-07-18 20:29 ` Vinson Lee
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=0000013f43718d4d-7bb260e7-8115-4891-bb26-6febacb7169d-000000@email.amazonses.com \
--to=cl@gentwo.org \
--cc=akpm@linux-foundation.org \
--cc=glommer@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=jiang.liu@huawei.com \
--cc=klamm@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mpm@selenic.com \
--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