linux-kernel - Re: [PATCH 04/10] block: initial patch for on-stack per-task plugging

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]

Date:	Thu, 10 Mar 2011 20:32:05 +0100
From:	Jens Axboe <jaxboe@...ionio.com>
To:	Vivek Goyal <vgoyal@...hat.com>
CC:	Jens Axboe <axboe@...nel.dk>, <linux-kernel@...r.kernel.org>,
	<hch@...radead.org>, Mike Snitzer <snitzer@...hat.com>
Subject: Re: [PATCH 04/10] block: initial patch for on-stack per-task plugging

On 2011-03-10 17:54, Vivek Goyal wrote:
> On Sat, Jan 22, 2011 at 01:17:23AM +0000, Jens Axboe wrote:
> 
> [..]
>> -/*
>> - * Only disabling plugging for non-rotational devices if it does tagging
>> - * as well, otherwise we do need the proper merging
>> - */
>> -static inline bool queue_should_plug(struct request_queue *q)
>> -{
>> -	return !(blk_queue_nonrot(q) && blk_queue_tagged(q));
>> -}
>> -
> 
> Jens,
> 
> While discussing stack plug with Mike Snitzer, this occurred to us that in
> new code we seem to be plugging even if underlying device is SSD with NCQ.
> Should we continue to maintain the old behavior of not plugging for NCQ SSD?

The main reason plugging was turned off for SSD's previously was because
it ended up hammering on the queue lock a lot. So it was turned off to
speed them up.

The new plugging scheme is faster than hitting the queue directly, so
now it would be a good idea to do the plugging in fact. Plus even for
high performance SSD's, things like merging are still a good idea.

So yes, it's on now and on purpose.

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