linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vinson Lee <vlee@freedesktop.org>
To: David Rientjes <rientjes@google.com>
Cc: Roman Gushchin <klamm@yandex-team.ru>,
	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,
	li@jasper.es
Subject: Re: [PATCH] slub: Avoid direct compaction if possible
Date: Thu, 18 Jul 2013 13:29:29 -0700	[thread overview]
Message-ID: <CACKvgLF7TKAJ1CFg=9vtk0Azga0mm02devKFbh2YGLCap2NcRA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306271340240.17334@chino.kir.corp.google.com>

On Thu, Jun 27, 2013 at 1:41 PM, David Rientjes <rientjes@google.com> wrote:
> On Thu, 27 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.
>>
>
> Yeah, we had significant problems with memory compaction in 3.3 and 3.4
> kernels, so if you need to run with such a kernel you'll want to backport
> the listed commits.  I'm not sure we could get such invasive changes into
> a stable release, unfortunately.

Hi.

Can the diff with the backport of the listed patches be posted? The
patches don't easily apply to 3.4.

I think I'm seeing memory compaction issues as well with Linux kernel
3.4 and would welcome any help. I'm planning to try the backporting
approach to see if it improves things on my side.

Cheers,
Vinson

--
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>

      reply	other threads:[~2013-07-18 20:29 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
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 [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='CACKvgLF7TKAJ1CFg=9vtk0Azga0mm02devKFbh2YGLCap2NcRA@mail.gmail.com' \
    --to=vlee@freedesktop.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@gentwo.org \
    --cc=glommer@parallels.com \
    --cc=hannes@cmpxchg.org \
    --cc=jiang.liu@huawei.com \
    --cc=klamm@yandex-team.ru \
    --cc=li@jasper.es \
    --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