From: Andrew Morton <akpm@google.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: performance regression due to recent block changes
Date: Thu, 21 Dec 2006 11:15:11 -0800 [thread overview]
Message-ID: <20061221111511.c3897be6.akpm@google.com> (raw)
Jens, the elapsed time for `mkefs2 /dev/hdc5' has just gone from nine
seconds to sixty, with the anticipatory scheduler (at least). It is due to
your recent merge.
This is the enty enth time that block changes have been slammed into
mainline without having had any exposure to -mm testers or even to me
personally. And it's the second time obvious regressions have gone in as a
result. I have a New Year's resolution for you ;)
reply other threads:[~2006-12-21 19:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061221111511.c3897be6.akpm@google.com \
--to=akpm@google.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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