All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Nick Piggin" <npiggin@kernel.dk>,
	Stewart Smith <stewart@flamingspork.com>
Subject: Re: RFC: mincore: add a bit to indicate a page is dirty.
Date: Tue, 12 Feb 2013 16:19:29 +1030	[thread overview]
Message-ID: <87pq06f5ee.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20130211162701.GB13218@cmpxchg.org>

Johannes Weiner <hannes@cmpxchg.org> writes:

> On Mon, Feb 11, 2013 at 01:43:03PM +1030, Rusty Russell wrote:
>> I am writing an app which really wants to know if a file is on the
>> disk or not (ie. do I need to sync?).
>
> When the page is under writeback, it's not necessarily on disk yet,
> but you also don't need to sync.  Which semantics make more sense?
>
> I'm leaning toward checking both PG_dirty and PG_writeback.

If it's already under PG_writeback, you probably still need to wait for
it to finish if you're trying to ensure write ordering. ie. sync.

I've updated my patch by stealing your code.

Thanks!
Rusty.

      parent reply	other threads:[~2013-02-12  5:52 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11  3:13 RFC: mincore: add a bit to indicate a page is dirty Rusty Russell
2013-02-11 16:27 ` Johannes Weiner
2013-02-11 22:12   ` Andrew Morton
2013-02-12  5:44     ` Rusty Russell
2013-02-15  6:34     ` [patch 1/2] mm: fincore() Johannes Weiner
2013-02-15  6:34       ` Johannes Weiner
2013-02-15 20:39       ` David Miller
2013-02-15 20:39         ` David Miller
2013-02-15 21:14       ` Andrew Morton
2013-02-15 21:14         ` Andrew Morton
2013-02-15 22:28         ` Johannes Weiner
2013-02-15 22:28           ` Johannes Weiner
2013-02-15 22:34           ` Andrew Morton
2013-02-15 22:34             ` Andrew Morton
2013-02-15 21:27       ` Andrew Morton
2013-02-15 21:27         ` Andrew Morton
2013-02-15 23:13         ` Johannes Weiner
2013-02-15 23:13           ` Johannes Weiner
2013-02-15 23:42           ` Andrew Morton
2013-02-15 23:42             ` Andrew Morton
2013-02-16  4:23             ` Rusty Russell
2013-02-16  4:23               ` Rusty Russell
2013-02-17 22:51               ` Johannes Weiner
2013-02-17 22:51                 ` Johannes Weiner
2013-02-17 22:54               ` Andrew Morton
2013-02-17 22:54                 ` Andrew Morton
2013-05-29 14:53               ` Andres Freund
2013-05-29 14:53                 ` Andres Freund
2013-05-29 17:32                 ` Johannes Weiner
2013-05-29 17:32                   ` Johannes Weiner
2013-05-29 17:52                   ` Andres Freund
2013-05-29 17:52                     ` Andres Freund
2013-02-18  5:41             ` Rusty Russell
2013-02-18  5:41               ` Rusty Russell
2013-02-19 10:25       ` Simon Jeons
2013-02-19 10:25         ` Simon Jeons
2013-02-15  6:35     ` [patch 2/2] x86-64: hook up fincore() syscall Johannes Weiner
2013-02-15  6:35       ` Johannes Weiner
2013-02-12  5:49   ` Rusty Russell [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=87pq06f5ee.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@kernel.dk \
    --cc=stewart@flamingspork.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.