linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shuvabrata Ganguly <sganguly@cse.iitkgp.ernet.in>
To: linux MM <linux-mm@kvack.org>
Subject: Question about swap_in() in 2.2.16 ....
Date: Wed, 08 Nov 2000 01:32:26 -0500	[thread overview]
Message-ID: <3A08F37A.38C156C1@cse.iitkgp.ernet.in> (raw)

hi,

after the missing page has been swapped in this bit of code is
executed:-

if (!write_access || is_page_shared(page_map)) {
      set_pte(page_table, mk_pte(page, vma->vm_page_prot));
      return 1;
 }

Now this creates a read-only mapping  even if the access was a "write
acess"  ( if the page is shared ). Doesnt this mean that an additional
"write-protect" fault will be taken immediately when the process tries
to write again ? Or am i missing something here ?

joy

--
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/

             reply	other threads:[~2000-11-08  6:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-08  6:32 Shuvabrata Ganguly [this message]
2000-11-08 10:05 ` Stephen C. Tweedie
2000-11-10  4:23   ` Shuvabrata Ganguly
2000-11-10  9:56     ` 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=3A08F37A.38C156C1@cse.iitkgp.ernet.in \
    --to=sganguly@cse.iitkgp.ernet.in \
    --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