From: Russ Anderson <rja@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH 2/3] mm: Avoid putting a bad page back on the LRU v2
Date: Fri, 02 May 2008 02:33:08 +0000 [thread overview]
Message-ID: <20080502023307.GA1591@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805011810410.13527@schroedinger.engr.sgi.com>
On Thu, May 01, 2008 at 06:12:49PM -0700, Christoph Lameter wrote:
> On Thu, 1 May 2008, Russ Anderson wrote:
>
> > Index: linus/mm/migrate.c
> > =================================> > --- linus.orig/mm/migrate.c 2008-05-01 19:05:33.000000000 -0500
> > +++ linus/mm/migrate.c 2008-05-01 19:06:15.000000000 -0500
> > @@ -380,6 +380,7 @@ static void migrate_page_copy(struct pag
> > SetPageChecked(newpage);
> > if (PageMappedToDisk(page))
> > SetPageMappedToDisk(newpage);
> > + /* Do not migrate PG_memerror to the new page */
>
> Why is the comment here?
To let anyone that may think PG_memerror should get copied to
the new page that it should not. I can remove the comment.
> > if (PageDirty(page)) {
> > clear_page_dirty_for_io(page);
> > @@ -721,6 +722,8 @@ unlock:
> > */
> > list_del(&page->lru);
> > move_to_lru(page);
> > + if (PageMemError(page))
> > + totalbad_pages++;
>
> Wouldnt this be taken care of by the lru handling?
It is only for accounting purposes, keeping a count
of the bad pages.
> > +#ifdef CONFIG_PAGEFLAGS_EXTENDED
> > +PAGEFLAG(MemError, memerror)
> > +#else
> > +#define PageMemError(page) 0
>
> Use
>
> PAGEFLAG_FLAGS(MemError)
OK.
> > #include <linux/page-flags.h>
> >
> > -#define PAGE_FLAGS (1 << PG_lru | 1 << PG_private | 1 << PG_locked | \
> > +#define PAGE_FLAGS_BASE (1 << PG_lru | 1 << PG_private | 1 << PG_locked | \
> > 1 << PG_buddy | 1 << PG_writeback | \
> > 1 << PG_slab | 1 << PG_swapcache | 1 << PG_active)
> > +
> > +#ifdef CONFIG_PAGEFLAGS_EXTENDED
> > +#define PAGE_FLAGS (PAGE_FLAGS_BASE | 1UL << PG_memerror)
> > +#else
> > +#define PAGE_FLAGS (PAGE_FLAGS_BASE)
> > +#endif
> >
> > #define PAGE_FLAGS_RECLAIM (PAGE_FLAGS | 1 << PG_reclaim | 1 << PG_dirty)
> > #define PAGE_FLAGS_RESERVE (PAGE_FLAGS | 1 << PG_reserved)
>
> The groups of page flags could also be put into page-flags.h.
page-flags.h is where I originally put them. Since they are only used in
mm/page_alloc.c, I thought mm.h would be a more appropriate place.
I can put them in page-flags.h.
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
WARNING: multiple messages have this Message-ID (diff)
From: Russ Anderson <rja@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH 2/3] mm: Avoid putting a bad page back on the LRU v2
Date: Thu, 1 May 2008 21:33:08 -0500 [thread overview]
Message-ID: <20080502023307.GA1591@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805011810410.13527@schroedinger.engr.sgi.com>
On Thu, May 01, 2008 at 06:12:49PM -0700, Christoph Lameter wrote:
> On Thu, 1 May 2008, Russ Anderson wrote:
>
> > Index: linus/mm/migrate.c
> > ===================================================================
> > --- linus.orig/mm/migrate.c 2008-05-01 19:05:33.000000000 -0500
> > +++ linus/mm/migrate.c 2008-05-01 19:06:15.000000000 -0500
> > @@ -380,6 +380,7 @@ static void migrate_page_copy(struct pag
> > SetPageChecked(newpage);
> > if (PageMappedToDisk(page))
> > SetPageMappedToDisk(newpage);
> > + /* Do not migrate PG_memerror to the new page */
>
> Why is the comment here?
To let anyone that may think PG_memerror should get copied to
the new page that it should not. I can remove the comment.
> > if (PageDirty(page)) {
> > clear_page_dirty_for_io(page);
> > @@ -721,6 +722,8 @@ unlock:
> > */
> > list_del(&page->lru);
> > move_to_lru(page);
> > + if (PageMemError(page))
> > + totalbad_pages++;
>
> Wouldnt this be taken care of by the lru handling?
It is only for accounting purposes, keeping a count
of the bad pages.
> > +#ifdef CONFIG_PAGEFLAGS_EXTENDED
> > +PAGEFLAG(MemError, memerror)
> > +#else
> > +#define PageMemError(page) 0
>
> Use
>
> PAGEFLAG_FLAGS(MemError)
OK.
> > #include <linux/page-flags.h>
> >
> > -#define PAGE_FLAGS (1 << PG_lru | 1 << PG_private | 1 << PG_locked | \
> > +#define PAGE_FLAGS_BASE (1 << PG_lru | 1 << PG_private | 1 << PG_locked | \
> > 1 << PG_buddy | 1 << PG_writeback | \
> > 1 << PG_slab | 1 << PG_swapcache | 1 << PG_active)
> > +
> > +#ifdef CONFIG_PAGEFLAGS_EXTENDED
> > +#define PAGE_FLAGS (PAGE_FLAGS_BASE | 1UL << PG_memerror)
> > +#else
> > +#define PAGE_FLAGS (PAGE_FLAGS_BASE)
> > +#endif
> >
> > #define PAGE_FLAGS_RECLAIM (PAGE_FLAGS | 1 << PG_reclaim | 1 << PG_dirty)
> > #define PAGE_FLAGS_RESERVE (PAGE_FLAGS | 1 << PG_reserved)
>
> The groups of page flags could also be put into page-flags.h.
page-flags.h is where I originally put them. Since they are only used in
mm/page_alloc.c, I thought mm.h would be a more appropriate place.
I can put them in page-flags.h.
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
next prev parent reply other threads:[~2008-05-02 2:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 0:42 [PATCH 2/3] mm: Avoid putting a bad page back on the LRU v2 Russ Anderson
2008-05-02 0:42 ` Russ Anderson
2008-05-02 1:12 ` Christoph Lameter
2008-05-02 1:12 ` Christoph Lameter
2008-05-02 2:33 ` Russ Anderson [this message]
2008-05-02 2:33 ` Russ Anderson
2008-05-09 15:10 ` [PATCH 2/3] mm: Avoid putting a bad page back on the LRU v3 Russ Anderson
2008-05-09 15:10 ` Russ Anderson
2008-05-09 20:11 ` Andrew Morton
2008-05-09 20:11 ` Andrew Morton
2008-05-09 21:51 ` Russ Anderson
2008-05-09 21:51 ` Russ Anderson
2008-05-13 23:03 ` [PATCH 2/3] mm: Avoid putting a bad page back on the LRU v4 Russ Anderson
2008-05-13 23:03 ` Russ Anderson
2008-05-16 19:23 ` [PATCH 2/3] mm: Avoid putting a bad page back on the LRU v5 Russ Anderson
2008-05-16 19:23 ` Russ Anderson
2008-05-16 23:13 ` Christoph Lameter
2008-05-16 23:13 ` Christoph Lameter
2008-06-09 15:57 ` Russ Anderson
2008-06-09 15:57 ` Russ Anderson
2008-06-09 16:19 ` [PATCH 2/3] mm: Avoid putting a bad page back on the LRU v6 Russ Anderson
2008-06-09 16:19 ` Russ Anderson
2008-06-09 18:28 ` Christoph Lameter
2008-06-09 18:28 ` Christoph Lameter
2008-06-09 21:03 ` Russ Anderson
2008-06-09 21:03 ` Russ Anderson
2008-06-09 21:15 ` Christoph Lameter
2008-06-09 21:15 ` Christoph Lameter
2008-06-09 21:58 ` [PATCH 2/3] mm: Avoid putting a bad page back on the LRU v7 Russ Anderson
2008-06-09 21:58 ` Russ Anderson
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=20080502023307.GA1591@sgi.com \
--to=rja@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
/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.