public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: Linux 2.4.34-pre3
Date: Tue, 19 Sep 2006 22:20:29 +0200	[thread overview]
Message-ID: <20060919202029.GA4017@1wt.eu> (raw)
In-Reply-To: <45103D1D.20702@yahoo.com.au>

On Wed, Sep 20, 2006 at 04:55:25AM +1000, Nick Piggin wrote:
> Willy Tarreau wrote:
> >Hi Nick,
> >
> >On Wed, Sep 20, 2006 at 03:42:06AM +1000, Nick Piggin wrote:
> >
> >[cut -pre3 advertisement]
> >
> >
> >>I wonder if 2.4 doesn't need the memory ordering fix to prevent pagecache
> >>corruption in reclaim? (http://www.gatago.com/linux/kernel/14682626.html)
> >>
> >>What would need to be done is to test page_count before testing PageDirty,
> >>and putting an smp_rmb between the two.
> >
> >
> >I've read the thread, and Linus proposed to add an smp_wmb() in
> >set_page_dirty() too.
> 
> I think that isn't needed because put_page is a RMW, which is defined
> to order memory. And presumably you wouldn't set the page dirty without
> a reference to the page.

OK, thanks for the explanation.

> >I see that an smp_rmb() is already present
> >in shrink_cache() with the adequate comment.
> 
> So there is! My mistake then, I was confused and looking at
> try_to_swap_out, but I see that doesn't actually free the page. Fine,
> I think 2.4 is OK then.

Perfect !

Thanks,
Willy


  reply	other threads:[~2006-09-19 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19 17:32 Linux 2.4.34-pre3 Willy Tarreau
2006-09-19 17:42 ` Nick Piggin
2006-09-19 18:17   ` Willy Tarreau
2006-09-19 18:55     ` Nick Piggin
2006-09-19 20:20       ` Willy Tarreau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-20 14:51 Mikael Pettersson
2006-09-20 16:41 ` Willy Tarreau

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=20060919202029.GA4017@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=nickpiggin@yahoo.com.au \
    /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