linux-kernel - Re: [PATCH BUGFIX/IMPROVEMENT V2 0/2] block, bfq: improve and refactor throughput-boosting logic

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]

Date:   Fri, 11 Aug 2017 08:58:30 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Paolo Valente <paolo.valente@...aro.org>
Cc:     linux-block <linux-block@...r.kernel.org>,
        linux-kernel@...r.kernel.org, ulf.hansson@...aro.org,
        broonie@...nel.org, lucmiccio@...il.com
Subject: Re: [PATCH BUGFIX/IMPROVEMENT V2 0/2] block, bfq: improve and
 refactor throughput-boosting logic

On 08/10/2017 01:55 PM, Paolo Valente wrote:
> 
>> Il giorno 04 ago 2017, alle ore 07:35, Paolo Valente <paolo.valente@...aro.org> ha scritto:
>>
>> Hi,
>> these two patches improve throughput-boosting logic in two
>> aspects. The first patch refactors the parts of the device-idling
>> logic, related to throughput boosting, that are still scattered across
>> the source file bfq-iosched.c. The patch concetrates all the logic in
>> one function. The second patch fixes/improves device idling for
>> flash-based devices that have no internal queueing of I/O requests.
>>
>> The contribution in the first patch has been triggered by that in the
>> second patch: finding the change made by the second patch has been
>> more difficult than it had to be, because the logic that decides
>> whether to idle the device is scattered across three functions.
>>
>> The second patch provides a significant throghput boost, for random
>> I/O with flash-based non-queueing devices. For example, on a HiKey
>> board, throughput increases by up to 125%, growing, e.g., from 6.9MB/s
>> to 15.6MB/s with two or three random readers in parallel.
>>
> 
> Hi Jens,
> any idea about the fate of these two patches?

Queued up for 4.14.

-- 
Jens Axboe