linux-kernel - Re: BLK_MQ_F_DEFER

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] [day] [month] [year] [list]

Message-ID: <x49pp6y7pmp.fsf@segfault.boston.devel.redhat.com>
Date:	Mon, 20 Apr 2015 12:04:14 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: BLK_MQ_F_DEFER_ISSUE

Jens Axboe <axboe@...nel.dk> writes:

> On 04/20/2015 09:09 AM, Jeff Moyer wrote:
>> Hi, Jens,
>>
>> This flag was introduced under the auspices that the nvme blk-mq
>> conversion would make use of it.  That never materialized.  Are there
>> still plans to make use of it?  If not, I'd like to get rid of it.  If
>> so, then let's document it better.
>
> Yep I still want to use it, and I do have a patch that uses it as well
> that I've run through testing. I thought I had pushed it somewhere,
> but it doesn't seem like I have. I just wanted to get the lower
> hanging optimizations out there first, like the kmalloc/kfree and
> queue-lock-for-completions removal. Former is in, latter is not yet.
>
> It's a useful optimization for lots of cases and I'm sure it'll see
> other uses, once the nvme patch is in. That will give people a
> reference point.

OK, thanks for the quick reply.

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