Hello Sir, I have a question about the I/O scheduler in kernel 5.2.9
in the new kernel, which I/O scheduler should be used by legacy rotating drive? Such as sata HDD? During FIO testing with libaio, I had create multiple thread in the testing, and then found 512k and bigger sequent write had bad performance result. Even I had enable and use BFQ scheduler. There has no sq scheduler anymore, only has none, mq-deadline, kyber and BFQ. Mq-deadline and kyber is for fast block device. Only the BFQ looks better performance, but it can't keep the good behavior during 512k or bigger 100% seq write. Could you give me some advices what parameter should I change for multiple thread bigger file seq writing? Thanks all of you. BestRegards, SunnyLiu(刘萍) LenovoNetApp 北京市海淀区西北旺东路10号院2号楼L3-E1-01 L3-E1-01,Building No.2, Lenovo HQ West No.10 XiBeiWang East Rd., Haidian District, Beijing 100094, PRC Tel: +86 15910622368 -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Hannes Reinecke Sent: 2019年9月19日 17:46 To: Jens Axboe <[email protected]> Cc: [email protected]; Martin K. Petersen <[email protected]>; James Bottomley <[email protected]>; Christoph Hellwig <[email protected]>; [email protected]; Hans Holmberg <[email protected]>; Damien Le Moal <[email protected]>; Hannes Reinecke <[email protected]> Subject: [RFC PATCH 0/2] blk-mq I/O scheduling fixes Hi all, Damien pointed out that there are some areas in the blk-mq I/O scheduling algorithm which have a distinct legacy feel to it, and prohibit multiqueue I/O schedulers from working properly. These two patches should clear up this situation, but as it's not quite clear what the original intention of the code was I'll be posting them as an RFC. So as usual, comments and reviews are welcome. Hannes Reinecke (2): blk-mq: fixup request re-insert in blk_mq_try_issue_list_directly() blk-mq: always call into the scheduler in blk_mq_make_request() block/blk-mq.c | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) -- 2.16.4
