linux-kernel - Re: [PATCH] slub: Avoid direct compaction if possible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1306271340240.17334@chino.kir.corp.google.com>
Date:	Thu, 27 Jun 2013 13:41:20 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Roman Gushchin <klamm@...dex-team.ru>
cc:	Michal Hocko <mhocko@...e.cz>, Christoph Lameter <cl@...two.org>,
	penberg@...nel.org, mpm@...enic.com, akpm@...ux-foundation.org,
	mgorman@...e.de, glommer@...allels.com, hannes@...xchg.org,
	minchan@...nel.org, jiang.liu@...wei.com, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] slub: Avoid direct compaction if possible

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/