Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754355AbbG2X5a (ORCPT ); Wed, 29 Jul 2015 19:57:30 -0400 Received: from ipmail06.adl2.internode.on.net ([150.101.137.129]:19976 "EHLO ipmail06.adl2.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754137AbbG2X52 (ORCPT ); Wed, 29 Jul 2015 19:57:28 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2ArCgBcZ7lVPG0mLHlbgxqBPYJVg3yiKAEBAQEBAQaafgQCAoFXTQEBAQEBAQcBAQEBQT+EJAEBBDocIxAIAw4KCSUPBSUDBxoTiC3POgEBAQcCIBmGBoUvhQcHhCwFlHKHXIRmmTKBCoMrLDGCTAEBAQ Date: Thu, 30 Jul 2015 09:57:25 +1000 From: Dave Chinner To: Vlastimil Babka Cc: David Rientjes , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrew Morton , Hugh Dickins , Andrea Arcangeli , "Kirill A. Shutemov" , Rik van Riel , Mel Gorman , Joonsoo Kim Subject: Re: [RFC 1/4] mm, compaction: introduce kcompactd Message-ID: <20150729235725.GN3902@dastard> References: <55AE0AFE.8070200@suse.cz> <55AFB569.90702@suse.cz> <55B0B175.9090306@suse.cz> <55B1DF11.8070100@suse.cz> <55B873DE.2060800@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55B873DE.2060800@suse.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1604 Lines: 37 On Wed, Jul 29, 2015 at 08:34:06AM +0200, Vlastimil Babka wrote: > On 07/29/2015 02:33 AM, David Rientjes wrote: > > On Fri, 24 Jul 2015, Vlastimil Babka wrote: > > > >> > Two issues I want to bring up: > >> > > >> > (1) do non-thp configs benefit from periodic compaction? > >> > > >> > In my experience, no, but perhaps there are other use cases where > >> > this has been a pain. The primary candidates, in my opinion, > >> > would be the networking stack and slub. Joonsoo reports having to > >> > workaround issues with high-order slub allocations being too > >> > expensive. I'm not sure that would be better served by periodic > >> > compaction, but it seems like a candidate for background compaction. > >> > >> Yes hopefully a proactive background compaction would serve them enough. > >> > >> > This is why my rfc tied periodic compaction to khugepaged, and we > >> > have strong evidence that this helps thp and cpu utilization. For > >> > periodic compaction to be possible outside of thp, we'd need a use > >> > case for it. Allowing us to use higher order pages in the page cache to support filesystem block sizes larger than page size without having to care about memory fragmentation preventing page cache allocation? Cheers, Dave. -- Dave Chinner david@fromorbit.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/