From: Dave Jones <davej@redhat.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Ben Gamari <bgamari.foss@gmail.com>,
David Rientjes <rientjes@google.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jesper Juhl <jj@chaosbits.net>
Subject: Re: [PATCH] Add Kconfig option for default swappiness
Date: Wed, 3 Nov 2010 10:33:59 -0400 [thread overview]
Message-ID: <20101103143358.GA19777@redhat.com> (raw)
In-Reply-To: <20101102140119.GA8294@localhost>
On Tue, Nov 02, 2010 at 10:01:20PM +0800, Wu Fengguang wrote:
> > On Mon, Nov 01, 2010 at 08:52:30AM -0400, Ben Gamari wrote:
> > > Ubuntu ships different kernels for desktop and server usage. From a
> > > packaging standpoint it would be much nicer to have this set in the
> > > kernel configuration. If we were to throw the setting /etc/sysctl.conf
> > > the kernel would depend upon the package containing sysctl(8)
> > > (procps). We'd rather avoid this and keep the default kernel
> > > configuration in one place.
> >
> > In short, being able to specify this default in .config is just far
> > simpler from a packaging standpoint than the alternatives.
>
> It's interesting to know what value you plan to use for your
> desktop/server systems and the rationals (is it based on any
> testing results?). And why it's easier to do it in kernel (hope it's
> not because of trouble communicating with the user space packaging
> team).
Not sure why I was cc'd on this, but at least for Fedora, we still take
the 'one kernel to rule them all' approach for every spin (and will likely
continue to do so to maximise coverage testing) so a config option for us
for things like this is moot.
Whenever I've tried to push changes to our defaults through to our
default /etc/sysctl.conf, it's been met with resistance due to beliefs
that a) the file is there for _users_ to override decisions
the distro made at build time and b) if this is the right default,
why isn't the kernel setting it?
The idea keeps coming up to have some userspace thing automatically
tune the kernel to dtrt based upon whatever profile it has been fed.
Various implementations of things like this have come and gone
(Arjan and myself even wrote one circa 2000). For whatever reason,
they don't seem to catch on.
Dave
--
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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-03 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 3:20 Ben Gamari
2010-11-02 3:33 ` David Rientjes
2010-11-02 12:58 ` Ben Gamari
2010-11-02 14:01 ` Wu Fengguang
2010-11-03 14:33 ` Dave Jones [this message]
2010-11-04 2:40 ` Ben Gamari
2010-11-04 3:09 ` Ben Gamari
2010-11-02 14:34 ` Hiroyuki Kamezawa
2010-11-04 2:44 ` Ben Gamari
2010-11-02 19:39 ` David Rientjes
2010-11-04 3:13 ` Ben Gamari
2010-11-02 4:14 ` Jesper Juhl
2010-11-02 4:27 ` Minchan Kim
2010-11-02 12:47 ` Hiroyuki Kamezawa
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=20101103143358.GA19777@redhat.com \
--to=davej@redhat.com \
--cc=bgamari.foss@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=jj@chaosbits.net \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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