linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: agl@us.ibm.com, wli@holomorphy.com, mel@csn.ul.ie,
	apw@shadowen.org, akpm@linux-foundation.org,
	lee.schermerhorn@hp.com, linux-mm@kvack.org
Subject: Re: [RFC][PATCH 1/2] hugetlb: introduce nr_overcommit_hugepages sysctl
Date: Thu, 13 Dec 2007 08:49:08 -0800	[thread overview]
Message-ID: <20071213164908.GE17526@us.ibm.com> (raw)
In-Reply-To: <20071213164453.GC17526@us.ibm.com>

On 13.12.2007 [08:44:53 -0800], Nishanth Aravamudan wrote:
> On 13.12.2007 [08:17:08 -0800], Dave Hansen wrote:
> > On Wed, 2007-12-12 at 23:41 -0800, Nishanth Aravamudan wrote:
> > > While examining the code to support /proc/sys/vm/hugetlb_dynamic_pool, I
> > > became convinced that having a boolean sysctl was insufficient:
> > > 
> > > 1) To support per-node control of hugepages, I have previously submitted
> > > patches to add a sysfs attribute related to nr_hugepages. However, with
> > > a boolean global value and per-mount quota enforcement constraining the
> > > dynamic pool, adding corresponding control of the dynamic pool on a
> > > per-node basis seems inconsistent to me.
> > 
> > Documentation/sysctl, please :)
> 
> Err, yes, will need to updated that. I note that the old sysctl is not
> there...nor is nr_hugepages, for that matter. So maybe I'll just add a
> 3rd patch to fix the Documentation? I really just wanted to get the
> patches out there as soon as I got them tested...

Hrm, nr_hugepages is documented in vm/hugetlbpage.txt and not
sysctl/vm.txt Should I document this sysctl there too?

Thanks,
Nish

-- 
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center

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

  reply	other threads:[~2007-12-13 16:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13  7:41 [RFC][PATCH 1/2] hugetlb: introduce nr_overcommit_hugepages sysctl Nishanth Aravamudan
2007-12-13  7:42 ` [RFC][PATCH 2/2] Revert "hugetlb: Add hugetlb_dynamic_pool sysctl" Nishanth Aravamudan
2007-12-13  8:53   ` William Lee Irwin III
2007-12-13 16:47     ` Nishanth Aravamudan
2007-12-13 17:37       ` William Lee Irwin III
2007-12-13 22:14   ` Adam Litke
2007-12-13 16:17 ` [RFC][PATCH 1/2] hugetlb: introduce nr_overcommit_hugepages sysctl Dave Hansen
2007-12-13 16:44   ` Nishanth Aravamudan
2007-12-13 16:49     ` Nishanth Aravamudan [this message]
2007-12-13 17:03       ` Dave Hansen
2007-12-13 17:02     ` Dave Hansen
2007-12-13 18:01       ` [RFC][PATCH 3/3] Documetation: update hugetlb information Nishanth Aravamudan
2007-12-13 18:01         ` Nishanth Aravamudan
2007-12-13 19:04         ` Dave Hansen
2007-12-13 19:20           ` Nishanth Aravamudan
2007-12-13 22:17         ` Adam Litke
2007-12-13 19:24 ` [RFC][PATCH 1/2] hugetlb: introduce nr_overcommit_hugepages sysctl Nishanth Aravamudan
2007-12-13 22:14 ` Adam Litke

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=20071213164908.GE17526@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=agl@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=haveblue@us.ibm.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=wli@holomorphy.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).