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:	Tue, 25 Nov 2014 12:48:48 +0800
From:	Gu Zheng <guz.fnst@...fujitsu.com>
To:	Jens Axboe <axboe@...nel.dk>
CC:	<kmo@...erainc.com>, <akpm@...ux-foundation.org>,
	<dm-devel@...hat.com>, <linux-kernel@...r.kernel.org>,
	<linux-nvme@...ts.infradead.org>, <drbd-user@...ts.linbit.com>
Subject: Re: [PATCH 0/6] blk: introduce generic io stat accounting help function

On 11/24/2014 11:03 PM, Jens Axboe wrote:

> On 11/23/2014 08:05 PM, Gu Zheng wrote:
>> Many block drivers accounting io stat based on bio (e.g. NVMe...),
>> the blk_account_io_start/end() which is based on request
>> does not make sense to them, so here we introduce the similar help
>> function named generic_start/end_io_acct base on raw sectors, and it can
>> simplify some driver's open io accounting code.
>>
>> Gu Zheng (6):
>>    blk: introduce generic io stat accounting help function
>>    NVMe: use generic io stat accounting functions to simplify
>>      nvme_start/end_io_acct
>>    md/bcache: use generic io stats accounting functions to simplify io
>>      stat accounting
>>    drbd: use generic io stats accounting functions to simplify io stat
>>      accounting
>>    md: use generic io stats accounting functions to simplify io stat
>>      accounting
>>    block/rsxx: use generic io stats accounting functions to simplify io
>>      stat accounting
> 
> Thanks, this looks good. I'll apply it, except 2/6, since nvme no longer uses them.

OK.

Thanks,
Gu

> 


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ