linux-kernel - Re: [PATCH V2 2/2] blk-mq: immediately dispatch big size request

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]

Message-ID: <20161104144614.GA18373@infradead.org>
Date:   Fri, 4 Nov 2016 07:46:14 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Jens Axboe <axboe@...com>
Cc:     Shaohua Li <shli@...com>, Christoph Hellwig <hch@...radead.org>,
        linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
        Kernel-team@...com
Subject: Re: [PATCH V2 2/2] blk-mq: immediately dispatch big size request

On Thu, Nov 03, 2016 at 10:00:58PM -0600, Jens Axboe wrote:
> I've applied 1-2 for 4.10, but we probably should look into unifying
> those parts of sq and mq in general. For instance, it doesn't seem to
> make a lot of sense why we'd depth limit sq and not mq.

I've spent some time looking the the make_request_fn and to be honest
I think that whole sq vs mq split is pointless.  They are about 70-80%
the same anyway, and I think everyone would be served much better
by merging them.