Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 6 Oct 2001 19:34:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 6 Oct 2001 19:34:11 -0400 Received: from shed.alex.org.uk ([195.224.53.219]:46773 "HELO shed.alex.org.uk") by vger.kernel.org with SMTP id ; Sat, 6 Oct 2001 19:33:56 -0400 Date: Sun, 07 Oct 2001 00:34:22 +0100 From: Alex Bligh - linux-kernel Reply-To: Alex Bligh - linux-kernel To: Mikulas Patocka , Alan Cox Cc: Anton Blanchard , 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: <482899202.1002414861@[195.224.237.69]> 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, 07 October, 2001 12:31 AM +0200 Mikulas Patocka wrote: > Sorry, but it can be triggered by _ANY_ VM since buddy allocator was > introduced. Just for info, this was circa 1.0.6 :-) (patches were available since 0.99.xxx). And before it was introduced, rather a lot of other things would consistently fail, for instance anything that reassembled packets whose total size was >4k. And currently they still need that. Kernel memory is a limited resource. Contiguous kernel memory more so. Things that need it need to better deal with the lack of it, esp. in transient situations (such as by working round the absence of it, e.g. kiovec in net code, or by causing some freeing and retrying). And, when contiguous kernel memory is short, the allocator could do with some intelligent page freeing to reduce fragmentation. -- 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/