Bart,
On 12/6/22 10:43, Bart Van Assche wrote:
> On 12/5/22 08:20, Alvaro Karsz wrote:
>> +/* Get lifetime information struct for each request */
>> +struct virtio_blk_lifetime {
>> + /*
>> + * specifies the percentage of reserved blocks that are consumed.
>> + * optional values
On Wed, Dec 07, 2022 at 10:19:08AM +0800, Yu Kuai wrote:
> Hi,
>
> 在 2022/12/07 2:15, Gulam Mohamed 写道:
> > Use ktime to change the granularity of IO accounting in block layer from
> > milli-seconds to nano-seconds to get the proper latency values for the
> > devices whose latency is in
Hi,
在 2022/12/07 2:15, Gulam Mohamed 写道:
Use ktime to change the granularity of IO accounting in block layer from
milli-seconds to nano-seconds to get the proper latency values for the
devices whose latency is in micro-seconds. After changing the granularity
to nano-seconds the iostat command,
On Sat, Dec 03, 2022 at 12:43:38AM +0100, mwi...@suse.com wrote:
> From: Martin Wilck
>
> To check whether we will be able to add a given device can be part
> of a multipath map, we have two tests in check_path_valid():
> released_to_systemd() and the O_EXCL test. The former isn't helpful
> if
Dear Gulam,
Thank you for the patch.
Am 06.12.22 um 19:15 schrieb Gulam Mohamed:
Use ktime to change the granularity of IO accounting in block layer from
milli-seconds to nano-seconds to get the proper latency values for the
devices whose latency is in micro-seconds. After changing the
On 12/6/22 06:40, Christoph Hellwig wrote:
This macro is obsolete, so replace the last few uses with open coded
bi_opf assignments.
For the entire patch:
Reviewed-by: Bart Van Assche
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
On 12/5/22 08:20, Alvaro Karsz wrote:
+/* Get lifetime information struct for each request */
+struct virtio_blk_lifetime {
+ /*
+* specifies the percentage of reserved blocks that are consumed.
+* optional values following virtio spec:
+* 0 - undefined
+* 1
Use ktime to change the granularity of IO accounting in block layer from
milli-seconds to nano-seconds to get the proper latency values for the
devices whose latency is in micro-seconds. After changing the granularity
to nano-seconds the iostat command, which was showing incorrect values for
This macro is obsolete, so replace the last few uses with open coded
bi_opf assignments.
Signed-off-by: Christoph Hellwig
---
drivers/md/bcache/movinggc.c | 2 +-
drivers/md/bcache/request.c | 2 +-
drivers/md/bcache/writeback.c | 4 ++--
drivers/md/dm-thin.c | 2 +-
> 2022年12月6日 22:40,Christoph Hellwig 写道:
>
> This macro is obsolete, so replace the last few uses with open coded
> bi_opf assignments.
>
> Signed-off-by: Christoph Hellwig
Acked-by: Coly Li mailto:col...@suse.de>>
BTW, may I ask why bio_set_op_attrs() is removed. Quite long time ago it
> 2022年12月6日 22:49,Christoph Hellwig 写道:
>
> On Tue, Dec 06, 2022 at 10:46:31PM +0800, Coly Li wrote:
>> BTW, may I ask why bio_set_op_attrs() is removed. Quite long time ago it was
>> added to avoid open code, and now we remove it to use open coded
>> assignments. What is the motivation for
On Tue, Dec 06, 2022 at 10:46:31PM +0800, Coly Li wrote:
> BTW, may I ask why bio_set_op_attrs() is removed. Quite long time ago it was
> added to avoid open code, and now we remove it to use open coded assignments.
> What is the motivation for now?
It was added when the flags encoding was a
12 matches
Mail list logo