From: Roman Gushchin <klamm@yandex-team.ru>
To: David Rientjes <rientjes@google.com>
Cc: Michal Hocko <mhocko@suse.cz>, Christoph Lameter <cl@gentwo.org>,
penberg@kernel.org, mpm@selenic.com, akpm@linux-foundation.org,
mgorman@suse.de, glommer@parallels.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: Thu, 27 Jun 2013 12:49:25 +0400 [thread overview]
Message-ID: <51CBFC95.9070002@yandex-team.ru> (raw)
In-Reply-To: <alpine.DEB.2.02.1306171441510.20631@chino.kir.corp.google.com>
On 18.06.2013 01:44, David Rientjes wrote:
> On Mon, 17 Jun 2013, Roman Gushchin wrote:
> They certainly aren't enough, the kernel you're running suffers from a
> couple different memory compaction issues that were fixed in 3.7. I
> couldn't sympathize with your situation more, I faced the same issue
> because of thp and not slub (we use slab).
>
>> I'll try to reproduce the issue on raw 3.9.
>>
I can't reproduce the issue on 3.9.
It seems that compaction fixes in 3.7 solve the problem.
>
> Thanks. If you need to go back to 3.4, try using these, they
> significantly helped our issues:
>
> bb13ffeb9f6bfeb301443994dfbf29f91117dfb3
> 627260595ca6abcb16d68a3732bac6b547e112d6
> c89511ab2f8fe2b47585e60da8af7fd213ec877e
> 62997027ca5b3d4618198ed8b1aba40b61b1137b
> a9aacbccf3145355190d87f0df1731fb84fdd8c8
Thank you!
Regards,
Roman
next prev parent reply other threads:[~2013-06-27 8:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 13:17 [PATCH] slub: Avoid direct compaction if possible Roman Gushchin
2013-06-14 14:32 ` Christoph Lameter
2013-06-14 15:17 ` Roman Gushchin
2013-06-14 16:08 ` Christoph Lameter
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 [this message]
2013-06-27 20:41 ` 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=51CBFC95.9070002@yandex-team.ru \
--to=klamm@yandex-team.ru \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=glommer@parallels.com \
--cc=hannes@cmpxchg.org \
--cc=jiang.liu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).