From: William Lee Irwin III <wli@holomorphy.com>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: agl@us.ibm.com, mel@csn.ul.ie, apw@shadowen.org,
akpm@linux-foundation.org, lee.schermerhorn@hp.com,
linux-mm@kvack.org
Subject: Re: [RFC][PATCH 2/2] Revert "hugetlb: Add hugetlb_dynamic_pool sysctl"
Date: Thu, 13 Dec 2007 09:37:24 -0800 [thread overview]
Message-ID: <20071213173724.GD31637@holomorphy.com> (raw)
In-Reply-To: <20071213164727.GD17526@us.ibm.com>
On 13.12.2007 [00:53:46 -0800], William Lee Irwin III wrote:
>> This is recent enough that dependencies shouldn't have developed, but
>> it'd be nice to stage user-visible API/ABI changes more consciously
>> and carefully in the future. Or at least we should try to avoid the
>> sorts of situations where we end up changing recently introduced
>> user/kernel ABI's and API's shortly after merging. We'll run the risk
>> of getting stuck with a user/kernel ABI we can't abandon for years on
>> account of not fixing it up before dependencies develop if this
>> happens too often.
On Thu, Dec 13, 2007 at 08:47:27AM -0800, Nishanth Aravamudan wrote:
> I agree and I apologize if I'm making things hard for everyone. However,
> I hadn't fully considered the implications of the dynamic pool for my
> other patches. The patches moved from -mm to -linus rather quickly,
> iirc. No excuse, however, I should have been paying more attention.
> If folks really don't want things to change, I guess we could also just
> make the sysctl's per-node corresponding attribute be a boolean too. It
> just seems less flexible than this approach.
I'm fine with this getting changed over since we've not spanned a point
release with the old nomenclature. If we had spanned a point release
there would be trouble. I've no particular preference about old vs. new
nomenclature apart from following user/kernel ABI/API stability rules.
-- wli
--
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>
next prev parent reply other threads:[~2007-12-13 17:37 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 [this message]
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
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=20071213173724.GD31637@holomorphy.com \
--to=wli@holomorphy.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=nacc@us.ibm.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).