From: Arjan van de Ven <arjan@infradead.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, lenb@kernel.org, mingo@elte.hu,
yanmin_zhang@linux.intel.com, jens.axboe@oracle.com,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: [PATCH v2] cpuidle: Fix the menu governor to boost IO performance
Date: Tue, 15 Sep 2009 06:18:44 +0200 [thread overview]
Message-ID: <20090915061844.3c92ee7a@infradead.org> (raw)
In-Reply-To: <20090915061512.0209d956@infradead.org>
On Tue, 15 Sep 2009 06:15:12 +0200
Arjan van de Ven <arjan@infradead.org> wrote:
>
> > The timing is awkward. We could let it sit in Len's tree and
> > linux-next for a couple of months or we could say what-the-hell and
> > merge it.
>
> If the performance impact wasn't this huge I'd say "let it sit".
> As it is now, with a nearly 2x performance delta, I'd not be very
> happy to expose linux users to this regression-like performance drop
> for another 3 months.
>
btw I do not like to use the "regression" word lightly, but kernels
prior to 2.6.22 or so did not have this performance drop (at least not
nearly as much), and current ones do.
next prev parent reply other threads:[~2009-09-15 4:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 3:42 [PATCH v2] cpuidle: Fix the menu governor to boost IO performance Arjan van de Ven
2009-09-15 3:54 ` Andrew Morton
2009-09-15 4:15 ` Arjan van de Ven
2009-09-15 4:18 ` Arjan van de Ven [this message]
2009-09-15 5:03 ` Rik van Riel
2009-09-15 23:23 ` Andrew Morton
2009-09-16 4:35 ` Arjan van de Ven
2009-09-17 13:39 ` Arjan van de Ven
2009-11-04 9:39 ` Corrado Zoccolo
2009-11-08 20:40 ` Arjan van de Ven
2009-11-08 21:59 ` Corrado Zoccolo
2009-11-08 22:30 ` Arjan van de Ven
2009-11-09 13:29 ` Corrado Zoccolo
2009-11-08 22:39 ` Arjan van de Ven
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=20090915061844.3c92ee7a@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jens.axboe@oracle.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yanmin_zhang@linux.intel.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