From: Alex Shi <alex.shi@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: aarcange@redhat.com, riel@redhat.com, mgorman@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] THP: need is_vma_temporary_stack() when reference transparent_hugepage_enabled
Date: Wed, 02 May 2012 11:31:20 +0800 [thread overview]
Message-ID: <4FA0AA88.5040900@intel.com> (raw)
In-Reply-To: <4FA0A743.2070904@intel.com>
>
> Oh, yes. Since is_vma_temporay_stack is just used in rmap.c and huge_memory.c
> . is it better to move it to huge_mm.h?
If you still concern someone just want to use is_vma_temporay_stack
function. I have no better idea. and please drop this patch if so. :)
next prev parent reply other threads:[~2012-05-02 3:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 6:33 [PATCH] THP: need is_vma_temporary_stack() when reference transparent_hugepage_enabled Alex Shi
2012-04-30 23:05 ` Andrew Morton
2012-05-02 3:17 ` Alex Shi
2012-05-02 3:31 ` Alex Shi [this message]
2012-05-02 17:55 ` Andrea Arcangeli
2012-05-03 0:56 ` Alex Shi
2012-05-03 11:25 ` Andrea Arcangeli
2012-05-04 7:26 ` Alex Shi
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=4FA0AA88.5040900@intel.com \
--to=alex.shi@intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=riel@redhat.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).