linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Jan Hudec <bulb@ucw.cz>, Martin Maletinsky <maletinsky@scs.ch>,
	linux-mm@kvack.org, kernelnewbies@nl.linux.org
Subject: Re: Question on set_page_dirty()
Date: Thu, 12 Dec 2002 10:29:30 +0100	[thread overview]
Message-ID: <20021212102930.C15158@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20021211080102.GG20525@vagabond>; from bulb@ucw.cz on Wed, Dec 11, 2002 at 09:01:02AM +0100

Hi,

On Wed, Dec 11, 2002 at 09:01:02AM +0100, Jan Hudec wrote:
> > What is the meaning of this dirty queue, what is the effect of linking
> > a page onto that queue, and when should the set_page_dirty() function
> > be used rather than the
> > SetPageDirty() macro?
> 
> If you use the SetPageDirty macro, then the page is marked dirty, but
> kernel can't find it when it should clean it. Thus it eventualy won't
> flush the data (it won't call writepage on it).

set_page_dirty() can be used in all cases, IMHO, since it:
   - will not sleep
   - will not call the set_page_dirty() method, if page has been dirty
     before (test_and_set_XXX is atomic an guarantees to trigger
     once only)
   - will not do anything besides settingt the PG_Dirty bit,
     if the page contains no mapping, or does not contain a
     set_page_dirty_method

So if set_page_dirty() exists on a certain kernel you want to
support, it should be used in all cases. Accounting code can also
be hooked into this, if it is used properly.

Regards

Ingo Oeser
-- 
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth
--
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-12-12  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  9:59 Martin Maletinsky
2002-12-11  8:01 ` Jan Hudec
2002-12-12  9:29   ` Ingo Oeser [this message]
2002-12-12 12:42     ` Stephen C. Tweedie
2002-12-12 18:20       ` Andrew Morton

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=20021212102930.C15158@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=bulb@ucw.cz \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-mm@kvack.org \
    --cc=maletinsky@scs.ch \
    /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