Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 8 Oct 2001 10:59:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 8 Oct 2001 10:59:04 -0400 Received: from shed.alex.org.uk ([195.224.53.219]:32698 "HELO shed.alex.org.uk") by vger.kernel.org with SMTP id ; Mon, 8 Oct 2001 10:58:54 -0400 Date: Mon, 08 Oct 2001 16:01:05 +0100 From: Alex Bligh - linux-kernel Reply-To: Alex Bligh - linux-kernel To: "Eric W. Biederman" , Alex Bligh - linux-kernel Cc: Mikulas Patocka , Rik van Riel , Krzysztof Rusocki , linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org, Alex Bligh - linux-kernel Subject: Re: %u-order allocation failed Message-ID: <1231218688.1002556865@[10.132.113.67]> In-Reply-To: In-Reply-To: X-Mailer: Mulberry/2.1.0 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org --On Sunday, October 07, 2001 12:30 PM -0600 "Eric W. Biederman" wrote: >> Note also that something (not sure what) has made fragmentation >> increasingly prevalent over the years since the buddy allocator >> was originally put in. > > Actually it seems to be situations like the stack now being two pages Instrumentation posted here before appears to corellate fragmentation being /caused/ with I/O activity (single bonnie process and thus a single 8k stack frame). My own guess is that it is due to a different persistence of various caches. I haven't seen anyone before blaming stack frame allocation as a /cause/ of fragmenation - I've heard people say they notice fragmentation more as stack frame allocs start to fail - but that's a symptom. -- Alex Bligh - 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/