From: Linus Torvalds <torvalds@transmeta.com>
To: "Eric W. Biederman" <ebiederm+eric@ccr.net>
Cc: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: [PATCH] cache large files in the page cache
Date: Sun, 30 May 1999 10:47:06 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.3.95.990530104226.18638J-100000@penguin.transmeta.com> (raw)
In-Reply-To: <m1675a4gv7.fsf@flinx.ccr.net>
On 30 May 1999, Eric W. Biederman wrote:
>
> LT> Indeed. An dI would suggest that the shift be limited to at most 9 anyway:
> LT> right now I applied the part that disallows non-page-aligned offsets, but
> LT> I think that we may in the future allow anonymous mappings again at finer
> LT> granularity (somebody made a really good argument about wine for this).
>
> I'd love to hear the argument. Something that would negate the disadvantage
> of ntuple buffering, and the need for reverse page maps, and isn't portable.
Wine.
Mapping windows binaries in a Linux address space.
Portability is a non-issue: this would only work on a 386, and only on
Linux anyway (MAYBE on other architectures Wine supports, but that's their
problem).
Windows binaries are _not_ nicely aligned like the Linux ones. They are
often 512-byte aligned.
Yes, we can read them in. That is slow as hell, and doesn't allow sharing.
Bad.
> Well, currectly supporting non-aligned mappings needs more than just a
> few extra bits. The code to update all mappings on write, and the
> ability to ensure that a given byte is only faulted in for a single
> offset at a time. (Admittedly if everything is a read mapping you
> can be a smidge more lax).
We would not guarantee write coherency for anything but the page-aligned
case.
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/
prev parent reply other threads:[~1999-05-30 17:47 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
1999-05-30 17:17 ` Eric W. Biederman
1999-05-30 17:47 ` Linus Torvalds [this message]
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.990530104226.18638J-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