[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070804212350.1b5b3aae@the-village.bc.nu>
Date: Sat, 4 Aug 2007 21:23:50 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Ingo Molnar <mingo@...e.hu>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, miklos@...redi.hu, neilb@...e.de,
dgc@....com, tomoki.sekiyama.qu@...achi.com, nikita@...sterfs.com,
trond.myklebust@....uio.no, yingchao.zhou@...il.com,
richard@....demon.co.uk
Subject: Re: [PATCH 00/23] per device dirty throttling -v8
> i tried to convince distro folks about it ... but there's fear,
> uncertainty and doubt about touching /etc/fstab and i suspect no major
> distro will do it until another does it - which is a catch-22 :-/ So i
Thats what Gentoo is for ;)
> guess we should add a kernel config option that allows the kernel rpm
> maker to just disable atime by default. (re-enableable via boot-line and
> fstab entry too) [That new kernel config option would be disabled by
> default.] That makes it much easier to control and introduce.
It makes it much more messy and awkward as the same system behaves in
arbitary different ways under different builds of the kernel.
If you want to sort this in Fedora for example you just need to package
and announce a desktop-tuning rpm which makes the relevant updates on
install and reverses them on remove. Stick the scheduler/vm tuning values
in as well and the disk queue tweaks.
Regardless of the kernel defaults people will install such a package
en-mass...
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists