From: ebiederm+eric@ccr.net (Eric W. Biederman)
To: linux-kernel@vger.rutgers.edu
Cc: linux-mm@kvack.org
Subject: Q: PAGE_CACHE_SIZE?
Date: 18 May 1999 09:03:57 -0500 [thread overview]
Message-ID: <m1yaimzd82.fsf@flinx.ccr.net> (raw)
Who's idea was it start the work to make the granularity of the page
cache larger?
>From what I can tell:
(a) It can save on finding multiple pages
(b) allows larger internal fragmentation of memory.
(c) Isn't needed if you just need a large chunk of the page
cache at a time. (It isn't hard to tie 2 or more pages to
together if you need to).
This is something I'm stumbling over porting patches for large
files in the page cache from 2.2.5 to to 2.3.3.
I guess if it's worth it I would like to talk with whoever is
responsible so we can coordinate our efforts.
Otherwise I would like this code dropped.
Non-page cache aligned mappings sound great until you
(a) squeeze the extra bits out of the vm_offset and make it an index
into the page cache, and
(b) realize you need more bits to say how far you are into a page.
Eric
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next reply other threads:[~1999-05-18 14:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-18 14:03 Eric W. Biederman [this message]
1999-05-18 15:04 ` Andi Kleen
1999-05-19 23:29 ` Chris Wedgwood
1999-05-20 17:12 ` Andrea Arcangeli
1999-05-25 16:29 ` Alan Cox
1999-05-25 20:16 ` Rik van Riel
1999-05-25 22:17 ` Matti Aarnio
1999-05-27 22:06 ` Alan Cox
1999-05-28 20:46 ` Stephen C. Tweedie
1999-05-28 21:33 ` Rik van Riel
1999-05-29 1:59 ` Stephen C. Tweedie
1999-05-30 23:12 ` Andrea Arcangeli
1999-06-01 0:01 ` Stephen C. Tweedie
1999-06-01 14:23 ` Andrea Arcangeli
1999-05-29 15:07 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1yaimzd82.fsf@flinx.ccr.net \
--to=ebiederm+eric@ccr.net \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox