From: "Luck, Tony" <tony.luck@intel.com>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.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 16:47:39 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F31CFEAC9@ORSMSX106.amr.corp.intel.com> (raw)
In-Reply-To: <20130917000817.GA5996@hacker.(null)>
> Transparent huge pages are not helpful for DB workload which there is a lot of
> shared memory
Hmm. Perhaps they should be. If a database allocates most[1] of the memory on a
machine to a shared memory segment - that *ought* to be a candidate for using
transparent huge pages. Now that we have them they seem a better choice (much
more flexibility) than hugetlbfs.
-Tony
[1] I've been told that it is normal to configure over 95% of physical memory to the
shared memory region to run a particular transaction based benchmark with one
commercial data base application.
--
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:[~2013-09-17 16:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 23:53 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
2013-09-16 23:44 ` Luck, Tony
2013-09-17 0:08 ` Wanpeng Li
2013-09-17 16:47 ` Luck, Tony [this message]
2013-09-17 0:08 ` Wanpeng Li
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=3908561D78D1C84285E8C5FCA982C28F31CFEAC9@ORSMSX106.amr.corp.intel.com \
--to=tony.luck@intel.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=liwanp@linux.vnet.ibm.com \
--cc=n-horiguchi@ah.jp.nec.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