Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261632AbUJ0Evg (ORCPT ); Wed, 27 Oct 2004 00:51:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261630AbUJ0Eve (ORCPT ); Wed, 27 Oct 2004 00:51:34 -0400 Received: from mx1.redhat.com ([66.187.233.31]:28324 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S261635AbUJ0EvP (ORCPT ); Wed, 27 Oct 2004 00:51:15 -0400 Date: Wed, 27 Oct 2004 00:51:11 -0400 (EDT) From: Rik van Riel X-X-Sender: riel@chimarrao.boston.redhat.com To: Andrea Arcangeli cc: Andrew Morton , Nick Piggin , Subject: Re: lowmem_reserve (replaces protection) In-Reply-To: <20041027044445.GV14325@dualathlon.random> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1065 Lines: 25 On Wed, 27 Oct 2004, Andrea Arcangeli wrote: > what we'll happen is that we'll blindly free a few pages from each zone, > but then we'll be allowed to allocate the highmem pages, and not the > normal/dma pages. So after allocating the highmem pages we invoke kswapd > again and it frees again some highmem/normal/dma pages but we keep only > using the highmem ones. So for a while we may be rolling over only the > highmem lru and ignoring all freed pages from the normal/dma zones. This is not how the page allocator in 2.6 works. It will not wake up kswapd until it is past the low watermark in all zones. -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - 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/