From: Nick Piggin <npiggin@suse.de>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
"Lee.Schermerhorn@hp.com" <Lee.Schermerhorn@hp.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] [8/16] HWPOISON: Use bitmask/action code for try_to_unmap behaviour
Date: Wed, 10 Jun 2009 08:07:54 +0200 [thread overview]
Message-ID: <20090610060754.GB31155@wotan.suse.de> (raw)
In-Reply-To: <20090610022736.GC6597@localhost>
On Wed, Jun 10, 2009 at 10:27:36AM +0800, Wu Fengguang wrote:
> On Tue, Jun 09, 2009 at 05:57:25PM +0800, Nick Piggin wrote:
> > On Wed, Jun 03, 2009 at 08:46:41PM +0200, Andi Kleen wrote:
> > >
> > > try_to_unmap currently has multiple modi (migration, munlock, normal unmap)
> > > which are selected by magic flag variables. The logic is not very straight
> > > forward, because each of these flag change multiple behaviours (e.g.
> > > migration turns off aging, not only sets up migration ptes etc.)
> > > Also the different flags interact in magic ways.
> > >
> > > A later patch in this series adds another mode to try_to_unmap, so
> > > this becomes quickly unmanageable.
> > >
> > > Replace the different flags with a action code (migration, munlock, munmap)
> > > and some additional flags as modifiers (ignore mlock, ignore aging).
> > > This makes the logic more straight forward and allows easier extension
> > > to new behaviours. Change all the caller to declare what they want to
> > > do.
> > >
> > > This patch is supposed to be a nop in behaviour. If anyone can prove
> > > it is not that would be a bug.
> > >
> > > Cc: Lee.Schermerhorn@hp.com
> > > Cc: npiggin@suse.de
> > >
> > > Signed-off-by: Andi Kleen <ak@linux.intel.com>
> > >
> > > ---
> > > include/linux/rmap.h | 14 +++++++++++++-
> > > mm/migrate.c | 2 +-
> > > mm/rmap.c | 40 ++++++++++++++++++++++------------------
> > > mm/vmscan.c | 2 +-
> > > 4 files changed, 37 insertions(+), 21 deletions(-)
> > >
> > > Index: linux/include/linux/rmap.h
> > > ===================================================================
> > > --- linux.orig/include/linux/rmap.h 2009-06-03 19:36:23.000000000 +0200
> > > +++ linux/include/linux/rmap.h 2009-06-03 20:39:50.000000000 +0200
> > > @@ -84,7 +84,19 @@
> > > * Called from mm/vmscan.c to handle paging out
> > > */
> > > int page_referenced(struct page *, int is_locked, struct mem_cgroup *cnt);
> > > -int try_to_unmap(struct page *, int ignore_refs);
> > > +
> > > +enum ttu_flags {
> > > + TTU_UNMAP = 0, /* unmap mode */
> > > + TTU_MIGRATION = 1, /* migration mode */
> > > + TTU_MUNLOCK = 2, /* munlock mode */
> > > + TTU_ACTION_MASK = 0xff,
> > > +
> > > + TTU_IGNORE_MLOCK = (1 << 8), /* ignore mlock */
> > > + TTU_IGNORE_ACCESS = (1 << 9), /* don't age */
> > > +};
> > > +#define TTU_ACTION(x) ((x) & TTU_ACTION_MASK)
> >
> > I still think this is nasty and should work like Gfp flags.
>
> I don't see big problems here.
>
> We have page_zone() and gfp_zone(), so why not TTU_ACTION()? We could
> allocate one bit for each action code, but in principle they are exclusive.
I haven't actually applied the patchset and looked at the resulting
try_to_unmap function, so I'll hold my tounge until I do that. I'll
send a patch if I can find something that looks nicer. So don't worry
about it for the moment.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-06-10 6:07 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 18:46 [PATCH] [0/16] HWPOISON: Intro Andi Kleen
2009-06-03 18:46 ` [PATCH] [1/16] HWPOISON: Add page flag for poisoned pages Andi Kleen
2009-06-03 18:46 ` [PATCH] [2/16] HWPOISON: Export some rmap vma locking to outside world Andi Kleen
2009-06-03 18:46 ` [PATCH] [3/16] HWPOISON: Add support for poison swap entries v2 Andi Kleen
2009-06-03 18:46 ` [PATCH] [4/16] HWPOISON: Add new SIGBUS error codes for hardware poison signals Andi Kleen
2009-06-03 18:46 ` [PATCH] [5/16] HWPOISON: Add basic support for poisoned pages in fault handler v3 Andi Kleen
2009-06-03 18:46 ` [PATCH] [6/16] HWPOISON: Add various poison checks in mm/memory.c Andi Kleen
2009-06-04 4:26 ` Wu Fengguang
2009-06-04 5:19 ` Andi Kleen
2009-06-04 11:55 ` Wu Fengguang
2009-06-04 12:52 ` Andi Kleen
2009-06-04 12:50 ` Wu Fengguang
2009-06-04 13:02 ` Andi Kleen
2009-06-04 13:16 ` Wu Fengguang
2009-06-09 10:25 ` Nick Piggin
2009-06-09 12:21 ` Wu Fengguang
2009-06-09 12:35 ` Nick Piggin
2009-06-03 18:46 ` [PATCH] [7/16] HWPOISON: x86: Add VM_FAULT_HWPOISON handling to x86 page fault handler v2 Andi Kleen
2009-06-09 9:54 ` Nick Piggin
2009-06-09 12:34 ` [PATCH] HWPOISON: define VM_FAULT_HWPOISON to 0 when feature is disabled Wu Fengguang
2009-06-03 18:46 ` [PATCH] [8/16] HWPOISON: Use bitmask/action code for try_to_unmap behaviour Andi Kleen
2009-06-09 9:57 ` Nick Piggin
2009-06-10 2:27 ` Wu Fengguang
2009-06-10 6:07 ` Nick Piggin [this message]
2009-06-03 18:46 ` [PATCH] [9/16] HWPOISON: Handle hardware poisoned pages in try_to_unmap Andi Kleen
2009-06-04 4:35 ` Wu Fengguang
2009-06-04 5:21 ` Andi Kleen
2009-06-03 18:46 ` [PATCH] [10/16] HWPOISON: Handle poisoned pages in set_page_dirty() Andi Kleen
2009-06-04 0:36 ` Wu Fengguang
2009-06-04 5:27 ` Andi Kleen
2009-06-09 9:59 ` Nick Piggin
2009-06-09 12:51 ` Wu Fengguang
2009-06-03 18:46 ` [PATCH] [11/16] HWPOISON: check and isolate corrupted free pages v2 Andi Kleen
2009-06-09 10:02 ` Nick Piggin
2009-06-09 13:03 ` Wu Fengguang
2009-06-09 13:28 ` Nick Piggin
2009-06-09 13:49 ` Wu Fengguang
2009-06-09 13:55 ` Nick Piggin
2009-06-09 14:56 ` Wu Fengguang
2009-06-09 15:31 ` Nick Piggin
2009-06-03 18:46 ` [PATCH] [12/16] Refactor truncate to allow direct truncating of page Andi Kleen
2009-06-04 4:32 ` Wu Fengguang
2009-06-04 5:20 ` Andi Kleen
2009-06-03 18:46 ` [PATCH] [13/16] HWPOISON: The high level memory error handler in the VM v5 Andi Kleen
2009-06-04 3:24 ` Wu Fengguang
2009-06-04 5:13 ` Andi Kleen
2009-06-04 9:07 ` Wu Fengguang
2009-06-04 9:26 ` Andi Kleen
2009-06-09 9:51 ` Nick Piggin
2009-06-09 11:14 ` Nick Piggin
2009-06-09 10:09 ` Nick Piggin
2009-06-09 16:05 ` Hugh Dickins
2009-06-09 16:35 ` Nick Piggin
2009-06-10 8:38 ` Wu Fengguang
2009-06-10 8:59 ` Nick Piggin
2009-06-10 9:20 ` Wu Fengguang
2009-06-10 11:03 ` Nick Piggin
2009-06-10 12:16 ` Wu Fengguang
2009-06-10 12:36 ` Nick Piggin
2009-06-12 9:58 ` Andi Kleen
2009-06-10 3:10 ` [PATCH] HWPOISON: fix tasklist_lock/anon_vma locking order Wu Fengguang
2009-06-03 18:46 ` [PATCH] [14/16] HWPOISON: FOR TESTING: Enable memory failure code unconditionally Andi Kleen
2009-06-03 18:46 ` [PATCH] [15/16] HWPOISON: Add madvise() based injector for hardware poisoned pages v3 Andi Kleen
2009-06-03 18:46 ` [PATCH] [16/16] HWPOISON: Add simple debugfs interface to inject hwpoison on arbitary PFNs Andi Kleen
2009-06-09 10:20 ` [PATCH] [0/16] HWPOISON: Intro Nick Piggin
2009-06-10 9:07 ` Wu Fengguang
2009-06-10 9:18 ` Nick Piggin
2009-06-10 9:45 ` Wu Fengguang
2009-06-10 11:15 ` Nick Piggin
2009-06-10 12:36 ` Wu Fengguang
2009-06-10 12:47 ` Nick Piggin
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=20090610060754.GB31155@wotan.suse.de \
--to=npiggin@suse.de \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).