linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: "Joseph A. Knapka" <jknapka@earthlink.net>,
	Martin Maletinsky <maletinsky@scs.ch>,
	linux-mm@kvack.org, kernelnewbies@nl.linux.org
Subject: Re: kiobuf interface / PG_locked flag
Date: Fri, 13 Sep 2002 14:41:27 +0200	[thread overview]
Message-ID: <20020913124127.GB23303@artax.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20020912163308.I2273@redhat.com>

On Thu, Sep 12, 2002 at 04:33:08PM +0100, Stephen C. Tweedie wrote:
> Hi,
> 
> On Thu, Sep 12, 2002 at 09:24:56AM -0600, Joseph A. Knapka wrote:
> 
> > > I just read about the kiobuf interface in the Linux Device Driver book from Rubini/Corbet, and there is one point, which I don't understand:
> > > - map_user_kiobuf() forces the pages within a user space address range into physical memory, and increments their usage count, which subsequently prevents the pages from
> > > being swapped out.
> > 
> > While it's true that having a non-zero reference count will prevent
> > a page from being swapped out, such a page is still subject to
> > all normal VM operations. In particular, the VM might unmap
> > the page from your process, *decrement its reference count*, and
> > then swap it out.
> 
> No.  The VM may unmap the page, and it may allocate a swap entry for
> it, and it may decrement the reference count associated with any mmap
> of the page, but it will NOT decrement the refcount associated with
> the kiobuf itself, and will not evict the page from memory.
> 
> > > - lock_kiovec() sets the PG_locked flag for the pages in the kiobufs of a kiovec. The PG_locked flag prevents the pages from being swapped out, which is however already
> > > ensured by map_user_kiobuf().
> > 
> > I believe PG_locked will prevent the VM from unmapping the
> > page, which does, in fact, gaurantee that it won't be
> > swapped out.
> 
> The page will not be swapped out anyway.  You don't need to lock it to
> prevent that.  Locking may be useful if you want to serialise IO on a
> particular page, but if you don't need that, there's just no point in
> locking the pages.

Ref-counts protect from swapping out. But it's the PG_locked flag, that
protects from starting other IO. If you are writing, read must not
happen. If you are reading, nothing else at all must happen. So that's
the difference. map_use_kiobuf fault the pages in. lock_kiovec make
sure, that noone (else) is doing ANU IO on the pages.

--------------------------------------------------------------------------------
                  				- Jan Hudec `Bulb' <bulb@ucw.cz>
--
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/

  reply	other threads:[~2002-09-13 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12  8:48 Martin Maletinsky
2002-09-12 15:24 ` Joseph A. Knapka
2002-09-12 15:33   ` Stephen C. Tweedie
2002-09-13 12:41     ` Jan Hudec [this message]
2002-09-13 14:45       ` Stephen C. Tweedie
2002-09-15 15:54         ` Jan Hudec

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=20020913124127.GB23303@artax.karlin.mff.cuni.cz \
    --to=bulb@ucw.cz \
    --cc=jknapka@earthlink.net \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-mm@kvack.org \
    --cc=maletinsky@scs.ch \
    --cc=sct@redhat.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