From: "michael chang" <thenewme91@gmail.com>
To: "Con Kolivas" <kernel@kolivas.org>
Cc: "Chuck Ebbert" <cebbert@redhat.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: Sat, 17 Feb 2007 16:50:37 -0500 [thread overview]
Message-ID: <b14e81f00702171350p6dc93a92ncad14f172356d11e@mail.gmail.com> (raw)
In-Reply-To: <200702180800.07393.kernel@kolivas.org>
On 2/17/07, Con Kolivas <kernel@kolivas.org> wrote:
> 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.
The patch, the way it's written now -- is the default to build with
swap-prefetch, or build without by default? If the former, maybe it
would be more accepted if the latter was the default. (Of course, that
defeats the point for desktop users who add the patch and then wonder
why it doesn't work, but... *shrugs*)
> 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.
While I'm all for putting Con's patches into mainline, I'm worried
about what happens if you rip swap prefetch apart and (if the
unthinkable happens) somebody accidentally omits something or worse.
Then mainline would have even more reason to be suspicious of code
from you, Con. Unless you already ripped the swap prefetch patch into
the parts that mm-filesize_dependant_lru_cache_add.patch depend on and
the parts it doesn't, and check it's "sane" to use them
independently...
(I'd be WAY more suspicious of having "half" of swap prefetch than
having all of it. I hope that most of mainline agrees with me, but I
have a sneaking suspicion they don't.)
In any case, this "ripping"... would it make the reverse happen? i.e.
swap prefetch being dependent on
mm-filesize_dependant_lru_cache_add.patch instead?
--
~Mike
- Just the crazy copy cat.
next prev parent reply other threads:[~2007-02-17 21:50 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
2007-02-17 21:50 ` michael chang [this message]
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=b14e81f00702171350p6dc93a92ncad14f172356d11e@mail.gmail.com \
--to=thenewme91@gmail.com \
--cc=cebbert@redhat.com \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®