From: Christoph Rohland <cr@sap.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SHM_LOCK question
Date: Tue, 26 Feb 2002 14:46:37 +0100 [thread overview]
Message-ID: <m3heo49wzm.fsf@linux.wdf.sap-ag.de> (raw)
In-Reply-To: <200202252136.g1PLaWs25602@eng2.beaverton.ibm.com>
In-Reply-To: <200202252136.g1PLaWs25602@eng2.beaverton.ibm.com> (Badari Pulavarty's message of "Mon, 25 Feb 2002 13:36:32 -0800 (PST)")
Hi Badari,
On Mon, 25 Feb 2002, Badari Pulavarty wrote:
> I am trying to understand how SHM_LOCK works on 2.4.17.
> All I can see SHM_LOCKED set in shm_flags. I don't see how
> it is locking the pages (that are already existing or future
> pages). Can somebody explain ?
This flag prevents that the pages are written to swap. shmem_writepage
honors it. SHM_LOCK does _not_ force actually swapped out pages into
memory though.
Greetings
Christoph
prev parent reply other threads:[~2002-02-26 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 21:36 Badari Pulavarty
2002-02-26 13:46 ` Christoph Rohland [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=m3heo49wzm.fsf@linux.wdf.sap-ag.de \
--to=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®