From: "Stephen C. Tweedie" <sct@redhat.com>
To: pnilesh@in.ibm.com
Cc: "Stephen C. Tweedie" <sct@redhat.com>, linux-mm@kvack.org
Subject: Re: page->offset
Date: Wed, 12 Apr 2000 15:45:14 +0100 [thread overview]
Message-ID: <20000412154514.G7570@redhat.com> (raw)
In-Reply-To: <CA2568BF.00489645.00@d73mta05.au.ibm.com>; from pnilesh@in.ibm.com on Wed, Apr 12, 2000 at 06:34:21PM +0530
Hi,
On Wed, Apr 12, 2000 at 06:34:21PM +0530, pnilesh@in.ibm.com wrote:
>
> If a file is opened and from an offset which is not page aligned say from
> offset 10.
> When we read this file into the memory page ,where the first byte will be
> loaded into the memory ?
> In 2.2 the first byte of the page will be the 10th byte of the file.
> In 2.3 the first byte will be first byte in the file and 10th byte is the
> 10th in the file.
No. The cache will always be page aligned in both 2.2 and 2.3 for
all user IO and for all mmap()ed files. The _only_ case where we
allow non-aligned mappings is when the execve() syscall is executed
on a QMAGIC binary, in which case 2.2 will allow the mapping and
will page the binary in at unaligned offsets when page faults occur.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-04-12 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-12 13:04 page->offset pnilesh
2000-04-12 14:45 ` Stephen C. Tweedie [this message]
2000-04-12 15:29 ` page->offset Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2000-04-13 11:19 page->offset pnilesh
2000-04-13 4:53 page->offset pnilesh
2000-04-13 6:07 ` page->offset Matti Aarnio
2000-04-13 19:34 ` page->offset Andrea Arcangeli
2000-04-13 9:59 ` page->offset Stephen C. Tweedie
2000-04-12 10:07 page->offset pnilesh
2000-04-12 11:06 ` page->offset Stephen C. Tweedie
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=20000412154514.G7570@redhat.com \
--to=sct@redhat.com \
--cc=linux-mm@kvack.org \
--cc=pnilesh@in.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.