Re: The pagecache unloved in zone NORMAL?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/05/2013 05:50 PM, Zlatko Calusic wrote:

An excellent Konstantin's patch better described here
http://marc.info/?l=linux-mm&m=136731974301311 is already giving some
useful additional insight into this problem, just as I expected. Here's
the data after 31h of server uptime (also see the attached graph):

Node 0, zone    DMA32
     nr_inactive_file 443705
   avg_age_inactive_file: 362800
Node 0, zone   Normal
     nr_inactive_file 32832
   avg_age_inactive_file: 38760

I reckon that only aging of the inactive LRU lists is of the interest at
the moment, because there's currently a streaming I/O of about 8MB/s
that can be seen on the graphs. Here's how I decipher the numbers:

The only question I have is, is this a design mistake, or a plain bug?

I believe this is a bug.

I strongly believe that pages should be reclaimed at speed appropriate
to the LRU size.

I agree. Aging the pages in one zone 10x as fast as the pages in
another zone could throw off all kinds of things, including detecting
(and preserving) the system working set, page cache readahead thrashing,
etc...

--
All rights reversed

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]