[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090610085939.GE31155@wotan.suse.de>
Date: Wed, 10 Jun 2009 10:59:39 +0200
From: Nick Piggin <npiggin@...e.de>
To: Wu Fengguang <fengguang.wu@...el.com>
Cc: Hugh Dickins <hugh.dickins@...cali.co.uk>,
Andi Kleen <andi@...stfloor.org>,
"riel@...hat.com" <riel@...hat.com>,
"chris.mason@...cle.com" <chris.mason@...cle.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH] [13/16] HWPOISON: The high level memory error handler in the VM v5
On Wed, Jun 10, 2009 at 04:38:03PM +0800, Wu Fengguang wrote:
> On Wed, Jun 10, 2009 at 12:05:53AM +0800, Hugh Dickins wrote:
> > I think a much more sensible approach would be to follow the page
> > migration technique of replacing the page's ptes by a special swap-like
> > entry, then do the killing from do_swap_page() if a process actually
> > tries to access the page.
>
> We call that "late kill" and will be enabled when
> sysctl_memory_failure_early_kill=0. Its default value is 1.
What's the use of this? What are the tradeoffs, in what situations
should an admin set this sysctl one way or the other?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists