From: Daniel Phillips <phillips@bonn-fries.net>
To: hochakhung@netscape.net, linux-kernel@vger.kernel.org
Subject: Re: Lock the page
Date: Fri, 27 Jul 2001 14:56:21 +0200 [thread overview]
Message-ID: <01072714562107.00285@starship> (raw)
In-Reply-To: <03E90795.17A1F592.0F45C3B8@netscape.net>
In-Reply-To: <03E90795.17A1F592.0F45C3B8@netscape.net>
On Friday 27 July 2001 04:55, hochakhung@netscape.net wrote:
> After getting a page from alloc_pages(mask, order), is it necessary
> to lock the page to prevent it from being swapped out? Can I assume
> that I already have exclusive access to the page? Can I assume that
> the page is free and no other kernel control paths would use it?
You alloced it, it's yours. You haven't entered it into any managed
structure like the page cache, it's not on a lru list so it won't be
scanned by reclaim, and no page table entry points at it (except for
the kernel's own linear mapping if it's not a highuser page) so
virtual scanning won't find it either.
--
Daniel
prev parent reply other threads:[~2001-07-27 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 2:55 Lock the page hochakhung
2001-07-27 12:56 ` Daniel Phillips [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=01072714562107.00285@starship \
--to=phillips@bonn-fries.net \
--cc=hochakhung@netscape.net \
--cc=linux-kernel@vger.kernel.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