From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Russ Anderson <rja@sgi.com>
Cc: mingo@elte.hu, tglx@linutronix.de,
Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: Avoid putting a bad page back on the LRU v7
Date: Thu, 24 Jul 2008 00:44:34 +0000 [thread overview]
Message-ID: <200807241044.35027.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20080723221338.GB193408@sgi.com>
On Thursday 24 July 2008 08:13, Russ Anderson wrote:
> On Tue, Jul 22, 2008 at 12:42:10PM +1000, Nick Piggin wrote:
> > On Saturday 19 July 2008 06:36, Russ Anderson wrote:
> > > [PATCH 1/2] mm: Avoid putting a bad page back on the LRU v7
> > >
> > > Prevent a page with a physical memory error from being placed back
> > > on the LRU. A new page flag (PG_memerror) is added if
> > > CONFIG_PAGEFLAGS_EXTENDED is defined.
> > >
> > > Signed-off-by: Russ Anderson <rja@sgi.com>
> > > Reviewed-by: Christoph Lameter <clameter@sgi.com>
> > >
> > > ---
> > > include/linux/page-flags.h | 18 ++++++++++++++++--
> > > mm/migrate.c | 31 ++++++++++++++++++++++++++++++-
> > > mm/page_alloc.c | 13 ++++++++-----
> > > 3 files changed, 54 insertions(+), 8 deletions(-)
> > >
> > > Index: linux/mm/page_alloc.c
> > > =================================> > > --- linux.orig/mm/page_alloc.c 2008-07-18 15:15:48.000000000 -0500
> > > +++ linux/mm/page_alloc.c 2008-07-18 15:16:09.000000000 -0500
> > > @@ -602,10 +602,10 @@ static int prep_new_page(struct page *pa
> > > bad_page(page);
> > >
> > > /*
> > > - * For now, we report if PG_reserved was found set, but do not
> > > - * clear it, and do not allocate the page: as a safety net.
> > > + * For now, we report if PG_reserved or PG_memerror was found set,
> > > but + * do not clear it, and do not allocate the page: as a safety
> > > net. */
> > > - if (PageReserved(page))
> > > + if (PageReserved(page) || PageMemError(page))
> > > return 1;
> > >
> > > page->flags &= ~(1 << PG_uptodate | 1 << PG_error | 1 << PG_reclaim |
> > > @@ -2475,8 +2475,11 @@ static void setup_zone_migrate_reserve(s
> > > continue;
> > > page = pfn_to_page(pfn);
> > >
> > > - /* Blocks with reserved pages will never free, skip them. */
> > > - if (PageReserved(page))
> > > + /*
> > > + * Blocks with reserved pages or memory errors will never
> > > + * free, skip them.
> > > + */
> > > + if (PageReserved(page) || PageMemError(page))
> > > continue;
> > >
> > > block_migratetype = get_pageblock_migratetype(page);
> >
> > I don't like adding more branches like this into fastpaths like this. It
> > would make a lot more sense to me if you just had some private module
> > that does the job of isolating the page from the lru and/or elevating
> > their refcount so that they do not get put back on freelists.
>
> That is how it works. If PageMemError is set the migration code
> leaves the page with an elevated refcount. The PageMemError() check
> was to avoid reallocating the page was an additional safty net.
> I'll pull the checks.
Ah, if it's that easy, great, then I have no problems with the patch.
Note that I have no problems with putting a VM_BUG_ON(PageMemError())
or something like that instead -- perhaps not quite the safty net you
would like. But helpful for developers and testers, and it acts as a
helpful little comment.
prev parent reply other threads:[~2008-07-24 0:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 19:23 [PATCH 1/2] mm: Avoid putting a bad page back on the LRU Russ Anderson
2008-04-28 19:39 ` Christoph Lameter
2008-04-29 21:33 ` Andrew Morton
2008-04-29 14:17 ` Arjan van de Ven
2008-04-29 21:47 ` Russ Anderson
2008-07-18 20:36 ` [PATCH 1/2] mm: Avoid putting a bad page back on the LRU v7 Russ Anderson
2008-07-22 2:42 ` Nick Piggin
2008-07-23 22:13 ` Russ Anderson
2008-07-24 0:44 ` Nick Piggin [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=200807241044.35027.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rja@sgi.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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