From: Andrew Morton <akpm@linux-foundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
Andrea Arcangeli <aarcange@redhat.com>,
linux-mm@kvack.org, Mel Gorman <mel@csn.ul.ie>,
Johannes Weiner <jweiner@redhat.com>,
Rik van Riel <riel@redhat.com>, Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH] mm/thp: Use conventional format for boolean attributes
Date: Wed, 13 Apr 2011 12:19:25 -0700 [thread overview]
Message-ID: <20110413121925.55493041.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1104131202230.5563@chino.kir.corp.google.com>
On Wed, 13 Apr 2011 12:04:59 -0700 (PDT)
David Rientjes <rientjes@google.com> wrote:
> On Tue, 22 Mar 2011, Ben Hutchings wrote:
>
> > The conventional format for boolean attributes in sysfs is numeric
> > ("0" or "1" followed by new-line). Any boolean attribute can then be
> > read and written using a generic function. Using the strings
> > "yes [no]", "[yes] no" (read), "yes" and "no" (write) will frustrate
> > this.
> >
> > Cc'd to stable in order to change this before many scripts depend on
> > the current strings.
> >
>
> I agree with this in general, it's certainly the standard way of altering
> a boolean tunable throughout the kernel so it would be nice to use the
> same userspace libraries with THP.
yup.
It's a bit naughty to change the existing interface in 2.6.38.x but the time
window is small and few people will be affected and they were nuts to be
using 2.6.38.0 anyway ;)
I suppose we could support both the old and new formats for a while,
then retire the old format but I doubt if it's worth it.
Isn't there some user documentation which needs to be updated to
reflect this change? If not, why not? :)
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-04-13 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 5:45 Ben Hutchings
2011-04-13 19:04 ` David Rientjes
2011-04-13 19:19 ` Andrew Morton [this message]
2011-04-13 19:28 ` David Rientjes
2011-04-13 19:35 ` Andrea Arcangeli
2011-04-14 4:48 ` NeilBrown
2011-04-14 14:29 ` Andrea Arcangeli
2011-04-14 16:57 ` Ben Hutchings
2011-04-14 19:09 ` Andrew Morton
2011-04-14 19:50 ` David Rientjes
2011-04-13 19:31 ` Andrew Morton
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=20110413121925.55493041.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aarcange@redhat.com \
--cc=ben@decadent.org.uk \
--cc=hughd@google.com \
--cc=jweiner@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=riel@redhat.com \
--cc=rientjes@google.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