linux-kernel - Re: performance regression from block merge

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Dec 2006 20:35:50 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>
Subject: Re: performance regression from block merge

On Thu, Dec 21 2006, Andrew Morton wrote:
> 
> Jens, elapsed time for `mke2fs /dev/hdc5' with the anticipatory scheduler
> (at least) has gone from nine seconds to sixty as a result of the recent
> block merge.

About when? I'll double check and test here, I'm assuming you mean since
2.6.19?

> This is the enty enth time that block code has been slammed into mainline
> without having had exposure to -mm testers or even to me personally, and it
> it the second time (at least) that obvious regressions have occurred as a
> result.  I have a New Year's resolution for you ;)

I usually try and make sure that for-akpm is the same as for-linus, so
if you pull that then it'll go to -mm as well. Sometimes the window
isn't that big, I'll try and make sure it's seen at least one -mm before
going upstream.

-- 
Jens Axboe

-
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/