linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	Andi Kleen <andi@firstfloor.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Wu, Fengguang" <fengguang.wu@intel.com>,
	"gong.chen@linux.intel.com" <gong.chen@linux.intel.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH v2 1/4] mm/hwpoison: fix traverse hugetlbfs page to avoid printk flood
Date: Tue, 17 Sep 2013 07:23:45 +0800	[thread overview]
Message-ID: <20130916232345.GA3241@hacker.(null)> (raw)
In-Reply-To: <1379369397-ld8lbcn-mutt-n-horiguchi@ah.jp.nec.com>

On Mon, Sep 16, 2013 at 06:09:57PM -0400, Naoya Horiguchi wrote:
>On Mon, Sep 16, 2013 at 09:50:06PM +0000, Luck, Tony wrote:
>> This is good - but the real solution is to stop poisoning entire huge pages ... they should
>> be broken into 4K pages and just one 4K page should be poisoned.
>> 
>> Naoya Horiguchi: I thought that you were looking at this problem some months ago. Any progress?
>
>Sorry, I have no meaningful progress on this. Splitting hugepages is not
>a trivial operation, and introduce more complexity on hugetlbfs code.
>I don't hit on any usecase of it rather than memory failure, so I'm not
>sure that it's worth doing now.

Agreed. ;-)

Regards,
Wanpeng Li 

>
>Thanks,
>Naoya Horiguchi
>
>--
>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>

--
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>

  parent reply	other threads:[~2013-09-16 23:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-14 23:53 [RESEND PATCH v2 1/4] mm/hwpoison: fix traverse hugetlbfs page to avoid printk flood Wanpeng Li
2013-09-14 23:53 ` [RESEND PATCH v2 2/4] mm/hwpoison: fix miss catch transparent huge page Wanpeng Li
2013-09-15  0:14   ` Andi Kleen
2013-09-14 23:53 ` [RESEND PATCH v2 3/4] mm/hwpoison: fix false report 2nd try page recovery Wanpeng Li
2013-09-15  0:15   ` Andi Kleen
2013-09-14 23:53 ` [RESEND PATCH v2 4/4] mm/hwpoison: fix the lack of one reference count against poisoned page Wanpeng Li
2013-09-15  0:16   ` Andi Kleen
2013-09-15  0:13 ` [RESEND PATCH v2 1/4] mm/hwpoison: fix traverse hugetlbfs page to avoid printk flood Andi Kleen
2013-09-16 21:50   ` Luck, Tony
2013-09-16 22:09     ` Naoya Horiguchi
2013-09-16 23:23       ` Wanpeng Li
2013-09-16 23:23       ` Wanpeng Li [this message]
2013-09-16 23:44         ` Luck, Tony
2013-09-17  0:08           ` Wanpeng Li
2013-09-17  0:08           ` Wanpeng Li
2013-09-17 16:47             ` Luck, Tony

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='20130916232345.GA3241@hacker.(null)' \
    --to=liwanp@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=fengguang.wu@intel.com \
    --cc=gong.chen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --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;
as well as URLs for NNTP newsgroup(s).