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
| ||
|
Date: Wed, 30 Mar 2022 09:35:41 +0800 From: "yukuai (C)" <yukuai3@...wei.com> To: Jens Axboe <axboe@...nel.dk>, <andriy.shevchenko@...ux.intel.com>, <john.garry@...wei.com>, <ming.lei@...hat.com> CC: <linux-block@...r.kernel.org>, <linux-kernel@...r.kernel.org>, <yi.zhang@...wei.com> Subject: Re: [PATCH -next RFC 2/6] block: refactor to split bio thoroughly On 2022/03/29 20:46, Jens Axboe wrote: > On 3/29/22 3:40 AM, Yu Kuai wrote: >> Currently, the splited bio is handled first, and then continue to split >> the original bio. This patch tries to split the original bio thoroughly, >> so that it can be known in advance how many tags will be needed. > > This makes the bio almost 10% bigger in size, which is NOT something > that is just done casually and without strong reasoning. Hi, Thanks for taking time on this patchset, It's right this way is not appropriate. > > So please provide that, your commit message is completely missing > justification for why this change is useful or necessary. A good > commit always explains WHY the change needs to be made, yours is > simply stating WHAT is being done. The latter can be gleaned from > the code change anyway. > Thanks for the guidance, I'll pay attemtion to that carefully in future. For this patch, what I want to do is to gain information about how many tags will be needed for the big io before getting the first tag, and use that information to optimize wake up path. The problem in this patch is that adding two feilds in bio is a bad move. I was thinking that for segment split, I can get the information by caculating bio segments / queue max segments. Thanks, Kuai
Powered by blists - more mailing lists