lkml.org 
[lkml]   [2005]   [Jan]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH][1/2] adjust dirty threshold for lowmem-only mappings
On Sat, Dec 25, 2004 at 07:07:21PM -0800, William Lee Irwin III wrote:
>> The problem as posed is that the dirty memory limits are global, but

On Sun, Jan 02, 2005 at 05:10:08PM +0100, Andrea Arcangeli wrote:
> What do you mean with global? Global is one thing, but taking highmem
> into account for calculating the limit is another thing. The
> nr_free_buffer_pages exists exactly to avoid taking highmem into account
> for the dirty memory limits. 2.6 must also ignore highmem in the dirty
> memory limits like 2.4 does. I'd be surprised if somebody broke this in
> 2.6. As far as I can tell, while writing to a blkdev it cannot make any
> difference if you've 4G or 1G of ram because of that (I mean on x86 of
> course).

It's not used for any of these purposes in 2.6.x.


-- wli
-
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/

\
 
 \ /
  Last update: 2005-03-22 14:09    [W:1.087 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site