linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nai Xia <nai.xia@gmail.com>
To: linux-mm@kvack.org
Subject: multiple address_space mappings
Date: Sat, 16 May 2009 22:53:05 +0800	[thread overview]
Message-ID: <ab418ea90905160753v52d82b2bj3fe3c85ea167a811@mail.gmail.com> (raw)

Hi, all

It may be a stupid question. But if a page (composed of contiguous
blocks)on a disk was read through two different paths --- one from
mmap of a regular file and another is direct reading of the block
device. Can they share the same page frame ?  If they can, should this
page have two page->mappings ?
It they cannot (I think this maybe true), how should we consider this
inconsistency?

Thanks !

Regards,

Nai

--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

                 reply	other threads:[~2009-05-16 14:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ab418ea90905160753v52d82b2bj3fe3c85ea167a811@mail.gmail.com \
    --to=nai.xia@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).