From: "Jiang, Dave" <dave.jiang@intel.com>
To: Dave Hansen <dave@sr71.net>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"dhillf@gmail.com" <dhillf@gmail.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Mel Gorman <mgorman@suse.de>
Subject: Re: [v3][PATCH 0/2] v3: fix hugetlb vs. anon-thp copy page
Date: Mon, 18 Nov 2013 19:23:01 +0000 [thread overview]
Message-ID: <1384802581.72241.7.camel@djiang5-linux2.ch.intel.com> (raw)
In-Reply-To: <20131115225550.737E5C33@viggo.jf.intel.com>
On Fri, 2013-11-15 at 14:55 -0800, Dave Hansen wrote:
> This took some of Mel's comments in to consideration. Dave
> Jiang, could you retest this if you get a chance? These have
> only been lightly compile-tested.
>
Everything looks good.
Tested-by: Dave Jiang <dave.jiang@intel.com>
prev parent reply other threads:[~2013-11-18 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 22:55 [v3][PATCH 0/2] v3: fix hugetlb vs. anon-thp copy page Dave Hansen
2013-11-15 22:55 ` [v3][PATCH 1/2] mm: hugetlbfs: Add VM_BUG_ON()s to catch non-hugetlbfs pages Dave Hansen
2013-11-15 22:55 ` [v3][PATCH 2/2] mm: thp: give transparent hugepage code a separate copy_page Dave Hansen
2013-11-18 10:32 ` Mel Gorman
2013-11-18 18:51 ` [v3][PATCH 2/2] mm: thp: give transparent hugepage code aseparate copy_page Naoya Horiguchi
2013-11-18 18:54 ` [PATCH] mm: call cond_resched() per MAX_ORDER_NR_PAGES pages copy Naoya Horiguchi
2013-11-18 19:02 ` Dave Hansen
2013-11-18 20:20 ` Naoya Horiguchi
2013-11-18 20:48 ` Dave Hansen
2013-11-18 21:56 ` Naoya Horiguchi
2013-11-18 22:29 ` Dave Hansen
2013-11-19 0:34 ` Naoya Horiguchi
2013-11-18 19:23 ` Jiang, Dave [this message]
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=1384802581.72241.7.camel@djiang5-linux2.ch.intel.com \
--to=dave.jiang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave@sr71.net \
--cc=dhillf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).