linux-kernel - Re: [GIT PULL] block bits for 3.1-rc

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAMM=eLepBCf8T-ps-cGbnUphjt_cEkmcj8q4FLdO7_73OR0RQg@mail.gmail.com>
Date:	Sat, 20 Aug 2011 15:15:08 -0400
From:	Mike Snitzer <snitzer@...il.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Jens Axboe <jaxboe@...ionio.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] block bits for 3.1-rc

On Sat, Aug 20, 2011 at 1:41 PM, Christoph Hellwig <hch@...radead.org> wrote:
> On Fri, Aug 19, 2011 at 03:16:40PM +0200, Jens Axboe wrote:
>> - Revert of the CFQ meta data special treatment patch, it's been shown
>>   to regress a kernel build workload by about 10%. More investigation
>>   is needed, for 3.1 lets just back it out.
>
> Sorry, but you can't simply do that without any coordination.  We have
> added that marker to xfs now that the stupid special casing stopped,
> and turning it back on will cause us massive slowdows.  Next time
> please better coordinate this with its users.  In fact I have never
> seen this patch or a discussion on any mailinglist.

lkml.org archive doesn't have the full thread for some reason, but here it is:
http://www.gossamer-threads.com/lists/linux/kernel/1420370
--
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/