From: ebiederm+eric@ccr.net (Eric W. Biederman)
To: Matti Aarnio <matti.aarnio@sonera.fi>
Cc: "Eric W. Biederman" <ebiederm+eric@ccr.net>,
linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Subject: Re: Large-File support of 32-bit Linux v0.01 available!
Date: 27 Dec 1998 19:01:25 -0600 [thread overview]
Message-ID: <m1ww3d3wre.fsf@flinx.ccr.net> (raw)
In-Reply-To: Matti Aarnio's message of "Mon, 28 Dec 1998 00:04:37 +0200 (EET)"
>>>>> "MA" == Matti Aarnio <matti.aarnio@sonera.fi> writes:
>> I have some other logic mostly complete that keeps offset parameter in
>> the vm_area struct at 32 bits, and hopefully a greater chunck of the
>> page cache.
MA> You mean 'vm_offset' field ?
MA> There are 37 files with (sub)string 'vm_offset' in them.
MA> Changeing its type from current loff_t to pgoff_t would
MA> help finding its instances, I guess. (And thus ease locating
MA> places using it for page (non-)aligned things.)
I changed the name from vm_offset to vm_index. Works equally well.
As far as non page alinged things, the only instance I have heard of
to date was with a.out.
There are a lot of implications to changing vm_offset in filemap.c
that I'm just finishing working out.
That and putting tests to see if the file size is bigger than we can
handle in the page cache at approprate places.
I believe I started at the really efficient end and you started at the
functional end.
Makes life fun . . .
MA> That part about "a greater chunk" I don't understand, though.
Poorly worded, (Thinking to fast probably!)
My meaning was changing the meaning of vm_offset you remove potential
64bit calculations from a lot of places.
Eric
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-12-28 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-27 6:49 Eric W. Biederman
1998-12-27 22:04 ` Matti Aarnio
1998-12-28 1:01 ` Eric W. Biederman [this message]
1998-12-30 17:34 ` Eric W. Biederman
1998-12-30 16:29 ` Matti Aarnio
1998-12-30 20:04 ` Eric W. Biederman
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=m1ww3d3wre.fsf@flinx.ccr.net \
--to=ebiederm+eric@ccr.net \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=matti.aarnio@sonera.fi \
/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