[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: More info: 2.1.108 page cache performance on low memory
Hi,
On 13 Jul 1998 13:08:56 -0500, ebiederm+eric@npwt.net (Eric
W. Biederman) said:
>>>>>> "ST" == Stephen C Tweedie <sct@redhat.com> writes:
> 1) We have a minimum size for the buffer cache in percent of physical pages.
> Setting the minimum to 0% may help.
...
> Personally I think it is broken to set the limits of cache sizes
> (buffer & page) to anthing besides: max=100% min=0% by default.
Yep; I disabled those limits for the benchmarks I announced. Disabling
the ageing but keeping the limits in place still resulted in a
performance loss.
> 2) If we play with LRU list it may be most practical use page->next
> and page->prev fields for the list, and for truncate_inode_pages &&
> invalidate_inode_pages
Yikes --- for large files the proposal that we do
> do something like:
> for(i = 0; i < inode->i_size; i+= PAGE_SIZE) {
> page = find_in_page_cache(inode, i);
> if (page)
> /* remove it */
> ;
> }
will be disasterous. No, I think we still need the per-inode page
lists. When we eventually get an fsync() which works through the page
cache, this will become even more important.
--Stephen
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org