All of lore.kernel.org
 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 3/3] Documetation: update hugetlb information
Date: Thu, 13 Dec 2007 11:20:08 -0800	[thread overview]
Message-ID: <20071213192008.GH17526@us.ibm.com> (raw)
In-Reply-To: <1197572668.21438.34.camel@localhost>

On 13.12.2007 [11:04:28 -0800], Dave Hansen wrote:
> On Thu, 2007-12-13 at 10:01 -0800, Nishanth Aravamudan wrote:
> > +Caveat: Shrinking the pool via nr_hugepages while a surplus is in effect
> > +will allow the number of surplus huge pages to exceed the overcommit
> > +value, as the pool hugepages (which must have been in use for a surplus
> > +hugepages to be allocated) will become surplus hugepages.  As long as
> > +this condition holds, however, no more surplus huge pages will be
> > +allowed on the system until one of the two sysctls are increased
> > +sufficiently, or the surplus huge pages go out of use and are freed.
> 
> I guess you could, in theory, disallow the writes to the sysctl and
> return -EINVAL or -ENOSPC or something.  But, I think documenting it
> like this is probably OK by itself and is pretty sane behavior given
> the circumstances.  

That's true -- would complicate the sysctl callback which is currently
able to just use one of the generic functions.

I'm willing to investigate changing this, if there is interest.

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 19:21 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
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 [this message]
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=20071213192008.GH17526@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 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.