From: Con Kolivas <kernel@kolivas.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: michael chang <thenewme91@gmail.com>,
ck mailing list <ck@vds.kolivas.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [ck] Re: 2.6.20-ck1
Date: Sun, 18 Feb 2007 08:00:06 +1100 [thread overview]
Message-ID: <200702180800.07393.kernel@kolivas.org> (raw)
In-Reply-To: <45D74D34.5020201@redhat.com>
On Sunday 18 February 2007 05:45, Chuck Ebbert wrote:
> Con Kolivas wrote:
> > Maintainers are far too busy off testing code for
> > 16+ cpus, petabytes of disk storage and so on to try it for themselves.
> > Plus they worry incessantly that my patches may harm those precious
> > machines' performance...
>
> But the one I like, mm-filesize_dependant_lru_cache_add.patch,
> has an on-off switch.
>
> In other words it adds an option to do things differently.
> How could that possibly affect any workload if that option
> isn't enabled?
Swap prefetch not only has an on-off switch, you can even build your kernel
without it entirely so it costs even less than this patch... I'm not going to
support the argument that it might be built into the kernel and enabled
unknowingly and _then_ cause overhead.
Oh and this patch depends on some of the code from the swap prefetch patch
too. I guess since they're so suspicious of swap prefetch the swap prefetch
patch can be ripped apart for the portions of code required to make this
patch work.
Do you still want this patch for mainline?...
--
-ck
next prev parent reply other threads:[~2007-02-17 21:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 10:10 2.6.20-ck1 Con Kolivas
2007-02-16 15:47 ` 2.6.20-ck1 Malte Schröder
2007-02-16 21:35 ` 2.6.20-ck1 Edouard Gomez
2007-02-16 21:45 ` 2.6.20-ck1 Edouard Gomez
2007-02-17 0:53 ` 2.6.20-ck1 Chuck Ebbert
2007-02-17 1:13 ` 2.6.20-ck1 Con Kolivas
2007-02-17 2:15 ` [ck] 2.6.20-ck1 michael chang
2007-02-17 3:17 ` Con Kolivas
2007-02-17 17:28 ` michael chang
2007-02-17 18:45 ` Chuck Ebbert
2007-02-17 21:00 ` Con Kolivas [this message]
2007-02-17 21:50 ` michael chang
2007-02-17 23:47 ` Andrew Morton
2007-02-18 0:39 ` 2.6.20-ck1 Con Kolivas
2007-02-18 0:41 ` [ck] 2.6.20-ck1 Radoslaw Szkodzinski
2007-02-18 0:45 ` 2.6.20-ck1 Con Kolivas
2007-02-17 11:15 ` 2.6.20-ck1 Hugo Vanwoerkom
2007-02-18 2:14 ` 2.6.20-ck1 mdew .
2007-02-18 2:38 ` 2.6.20-ck1 Con Kolivas
2007-02-18 6:05 ` [ck] 2.6.20-ck1 Con Kolivas
2007-02-18 6:15 ` Rodney Gordon II
2007-02-18 6:20 ` Rodney Gordon II
2007-02-18 16:54 ` 2.6.20-ck1 Ryan M.
2007-02-18 19:00 ` [ck] 2.6.20-ck1 Ash Milsted
2007-02-24 12:12 ` 2.6.20-ck1 Fabio Comolli
2007-02-25 4:34 ` 2.6.20-ck1 Gene Heskett
2007-02-25 10:32 ` 2.6.20-ck1 Con Kolivas
2007-02-25 16:33 ` 2.6.20-ck1 Gene Heskett
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=200702180800.07393.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=cebbert@redhat.com \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thenewme91@gmail.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