linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Paul R. Wilson" <wilson@cs.utexas.edu>
Cc: linux-mm@kvack.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: question about try_to_swap_out()
Date: Tue, 12 Jan 1999 16:10:42 GMT	[thread overview]
Message-ID: <199901121610.QAA04831@dax.scot.redhat.com> (raw)
In-Reply-To: <199901110338.VAA19737@feta.cs.utexas.edu>

Hi,

On Sun, 10 Jan 1999 21:38:46 -0600, "Paul R. Wilson"
<wilson@cs.utexas.edu> said:

> After checking that that a page is present and pageable, try_to_swap_out()
> checks to see if the page is reserved or locked or not DMA'able when
> where looking for a DMA page.  If any of these three things is
> true, it returns 0 without changing anything.

> It seems to me that it should go ahead and check the pte age bit,
> and update the page frame's PG_referenced bit, before returning 0.

Not really.  Reserved pages never get swapped anyway.  For DMA, we don't
want to disturb non-DMA processes at all --- the demand for DMA and
non-DMA pages might be very different.  For locked pages, we expect this
to be sufficiently rare that it's totally irrelevant whether we age the
page or not.

> Am I off-base here, or should the conditional that checks to see
> whether a page is young (and updates the reference bits) be moved
> up ahead of the conditional that checks to see whether a page
> is (reserved | locked | not-dma-but-we-need-dma)?

I really don't think it's that important!

--Stephen
--
This is a majordomo managed list.  To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org

  reply	other threads:[~1999-01-12 16:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-11  3:38 Paul R. Wilson
1999-01-12 16:10 ` Stephen C. Tweedie [this message]
1999-01-12 16:58 Paul R. Wilson
1999-01-12 18:14 ` Stephen C. Tweedie
1999-01-14 10:15   ` ralf
1999-01-12 18:42 Paul R. Wilson

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=199901121610.QAA04831@dax.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=wilson@cs.utexas.edu \
    /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