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
| ||
|
Date: Thu, 12 May 2011 19:36:28 +0200 From: Andrea Arcangeli <aarcange@...hat.com> To: David Rientjes <rientjes@...gle.com> Cc: Mel Gorman <mgorman@...e.de>, Andrew Morton <akpm@...ux-foundation.org>, James Bottomley <James.Bottomley@...senpartnership.com>, Colin King <colin.king@...onical.com>, Raghavendra D Prabhu <raghu.prabhu13@...il.com>, Jan Kara <jack@...e.cz>, Chris Mason <chris.mason@...cle.com>, Christoph Lameter <cl@...ux.com>, Pekka Enberg <penberg@...nel.org>, Rik van Riel <riel@...hat.com>, Johannes Weiner <hannes@...xchg.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-mm <linux-mm@...ck.org>, linux-kernel <linux-kernel@...r.kernel.org>, linux-ext4 <linux-ext4@...r.kernel.org> Subject: Re: [PATCH 3/3] mm: slub: Default slub_max_order to 0 On Wed, May 11, 2011 at 01:38:47PM -0700, David Rientjes wrote: > kswapd and doing compaction for the higher order allocs before falling Note that patch 2 disabled compaction by clearing __GFP_WAIT. What you describe here would be patch 2 without the ~__GFP_WAIT addition (so keeping only ~GFP_NOFAIL). Not clearing __GFP_WAIT when compaction is enabled is possible and shouldn't result in bad behavior (if compaction is not enabled with current SLUB it's hard to imagine how it could perform decently if there's fragmentation). You should try to benchmark to see if it's worth it on the large NUMA systems with heavy network traffic (for normal systems I doubt compaction is worth it but I'm not against trying to keep it enabled just in case). On a side note, this reminds me to rebuild with slub_max_order in .bss on my cellphone (where I can't switch to SLAB because of some silly rfs vfat-on-steroids proprietary module). -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists