From: Michal Hocko <mhocko@suse.cz>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] Make swap accounting default behavior configurable v2
Date: Fri, 12 Nov 2010 09:31:03 +0100 [thread overview]
Message-ID: <20101112083103.GB7285@tiehlicka.suse.cz> (raw)
In-Reply-To: <20101112094118.b02b669f.nishimura@mxp.nes.nec.co.jp>
On Fri 12-11-10 09:41:18, Daisuke Nishimura wrote:
> On Thu, 11 Nov 2010 10:31:55 +0100
> Michal Hocko <mhocko@suse.cz> wrote:
>
> > On Thu 11-11-10 09:46:13, Daisuke Nishimura wrote:
> > > On Wed, 10 Nov 2010 13:51:54 +0100
> > > Michal Hocko <mhocko@suse.cz> wrote:
> > >
> > > > Hi,
> > > > could you consider the patch bellow? It basically changes the default
> > > > swap accounting behavior (when it is turned on in configuration) to be
> > > > configurable as well.
> > > >
> > > > The rationale is described in the patch but in short it makes it much
> > > > more easier to enable this feature in distribution kernels as the
> > > > functionality can be provided in the general purpose kernel (with the
> > > > option disabled) without any drawbacks and interested users can enable
> > > > it. This is not possible currently.
> > > >
> > > > I am aware that boot command line parameter name change is not ideal but
> > > > the original semantic wasn't good enough and I don't like
> > > > noswapaccount=yes|no very much.
> > > >
> > > > If we really have to stick to it I can rework the patch to keep the name
> > > > and just add the yes|no logic, though. Or we can keep the original one
> > > > and add swapaccount paramete which would mean the oposite as the other
> > > > one.
> > > >
> > > hmm, I agree that current parameter name(noswapaccount) is not desirable
> > > for yes|no, but IMHO changing the user interface(iow, making what worked before
> > > unusable) is worse.
> > >
> > > Although I'm not sure how many people are using this parameter, I vote for
> > > using "noswapaccount[=(yes|no)]".
> >
> > Isn't a new swapaccount parameter better than that? I know we don't want
> > to have too many parameters but having a something with a clear meaning
> > is better IMO (noswapaccount=no doesn't sound very intuitive to me).
> >
> Fair enough. It's just an trade-off between compatibility and understandability.
>
> > > And you should update Documentation/kernel-parameters.txt too.
> >
> > Yes, I am aware of that and will do that once there is an agreement on
> > the patch itself. At this stage, I just wanted to have a feadback about
> > the change.
> >
> I'll ack your patch when it's been released with documentation update.
Changes since v1:
* do not remove noswapaccount parameter and add swapaccount parameter
instead
* Documentation/kernel-parameters.txt updated
---
next prev parent reply other threads:[~2010-11-12 8:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 12:51 [RFC PATCH] Make swap accounting default behavior configurable Michal Hocko
2010-11-11 0:46 ` Daisuke Nishimura
2010-11-11 9:31 ` Michal Hocko
2010-11-12 0:41 ` Daisuke Nishimura
2010-11-12 8:31 ` Michal Hocko [this message]
2010-11-15 1:13 ` [RFC PATCH] Make swap accounting default behavior configurable v2 Daisuke Nishimura
2010-11-15 2:03 ` Balbir Singh
2010-11-15 2:31 ` Daisuke Nishimura
2010-11-15 8:35 ` [RFC PATCH] Make swap accounting default behavior configurable v3 Michal Hocko
2010-11-16 4:48 ` Daisuke Nishimura
2010-11-16 8:15 ` Michal Hocko
2010-11-16 10:03 ` Daisuke Nishimura
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=20101112083103.GB7285@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
/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