From: Rik van Riel <riel@redhat.com>
To: Alex Thorlton <athorlton@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@suse.de>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Sedat Dilek <sedat.dilek@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Dave Jones <davej@redhat.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
David Howells <dhowells@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Al Viro <viro@zeniv.linux.org.uk>,
Oleg Nesterov <oleg@redhat.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Kees Cook <keescook@chromium.org>, Robin Holt <holt@sgi.com>
Subject: Re: [PATCHv2] Add per-process flag to control thp
Date: Tue, 06 Aug 2013 12:04:41 -0400 [thread overview]
Message-ID: <52011E99.8030708@redhat.com> (raw)
In-Reply-To: <20130806150807.GA2456@sgi.com>
On 08/06/2013 11:08 AM, Alex Thorlton wrote:
> Thanks, Andrew. I'm doing some more testing and looking into using a
> different method for controlling this. At this point, I think it's fair
> to say that we don't want to control this using the method that I've
> proposed here, no matter how we look at it.
Considering that we have both mlock and mlockall, it
is not totally crazy to also have both madvise and
madviseall.
Just saying... :)
--
All rights reversed
next prev parent reply other threads:[~2013-08-06 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 20:57 [PATCHv2] Add per-process flag to control thp Alex Thorlton
2013-08-03 17:01 ` Oleg Nesterov
2013-08-05 14:45 ` Peter Zijlstra
2013-08-05 15:12 ` Alex Thorlton
2013-08-05 15:05 ` Alex Thorlton
2013-08-05 15:09 ` Rik van Riel
2013-08-05 23:03 ` Andrew Morton
2013-08-06 15:08 ` Alex Thorlton
2013-08-06 16:04 ` Rik van Riel [this message]
2013-08-08 3:49 ` David Rientjes
2013-08-11 16:56 ` Aneesh Kumar K.V
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=52011E99.8030708@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=athorlton@sgi.com \
--cc=davej@redhat.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=fweisbec@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=holt@sgi.com \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=sedat.dilek@gmail.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.