From: Linus Torvalds <torvalds@transmeta.com>
To: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
Cc: "Eric W. Biederman" <ebiederm+eric@ccr.net>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: [PATCH] cache large files in the page cache
Date: Wed, 26 May 1999 10:44:02 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.3.95.990526104127.14018K-100000@penguin.transmeta.com> (raw)
In-Reply-To: <19990526094407.J527@mff.cuni.cz>
On Wed, 26 May 1999, Jakub Jelinek wrote:
>
> I have minor suggestion to the patch. Instead of using vm_index <<
> PAGE_SHIFT and page->key << PAGE_CACHE_SHIFT shifts either choose different
> constant names for this shifting (VM_INDEX_SHIFT and PAGE_KEY_SHIFT) or hide
> these shifts by some pretty macros (you'll need two for each for both
> directions in that case - if you go the macro way, maybe it would be a good
> idea to make vm_index and key type some structure with a single member like
> mm_segment_t for more strict typechecking).
Indeed. An dI would suggest that the shift be limited to at most 9 anyway:
right now I applied the part that disallows non-page-aligned offsets, but
I think that we may in the future allow anonymous mappings again at finer
granularity (somebody made a really good argument about wine for this).
Thinking that the VM mapping shift has to be the same as the page shift is
not necessarily the right thing. With just 9 bits of shift, you still get
large files - 41 bits of files on a 32-bit architecture, and by the time
you want more you _really_ can say that you had better upgrade your CPU.
Linus
--
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 prev parent reply other threads:[~1999-05-26 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-23 19:28 Eric W. Biederman
1999-05-24 15:27 ` Andrea Arcangeli
1999-05-26 7:44 ` Jakub Jelinek
1999-05-26 17:44 ` Linus Torvalds [this message]
1999-05-30 17:17 ` Eric W. Biederman
1999-05-30 17:47 ` Linus Torvalds
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=Pine.LNX.3.95.990526104127.14018K-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=ebiederm+eric@ccr.net \
--cc=jj@sunsite.ms.mff.cuni.cz \
--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