[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7B4FF58E-BCF5-4997-8006-CEC5A3EDEB85@gmail.com>
Date: Thu, 15 May 2025 21:38:06 +0800
From: Yu Kuai <yukuai1994@...il.com>
To: Christoph Hellwig <hch@....de>, Yu Kuai <yukuai1@...weicloud.com>
CC: xni@...hat.com, colyli@...nel.org, agk@...hat.com, snitzer@...nel.org,
mpatocka@...hat.com, song@...nel.org, linux-kernel@...r.kernel.org,
dm-devel@...ts.linux.dev, linux-raid@...r.kernel.org, yi.zhang@...wei.com,
yangerkun@...wei.com, johnny.chenyi@...wei.com,
"yukuai (C)" <yukuai3@...wei.com>
Subject: Re: [PATCH RFC md-6.16 v3 15/19] md/md-llbitmap: implement APIs to dirty bits and clear bits
Hi
于 2025年5月14日 GMT+08:00 13:17:47,Christoph Hellwig <hch@....de> 写道:
>On Tue, May 13, 2025 at 05:32:13PM +0800, Yu Kuai wrote:
>> I was thinking about record a stack dev depth in mddev to handle the
>> weird case inside raid. Is there other stack device have the same
>> problem? AFAIK, some dm targets like dm-crypt are using workqueue
>> to handle all IO.
>
>I guess anything that might have to read in metadata to serve a
>data I/O. bcache, dm-snapshot and dm-thinkp would be candidates for
>that, but I haven't checked the implementation.
>
>> I'm still interested because this can improve first write latency.
>>
>>>
>>> So instead just write a comment documenting why you switch to a
>>> different stack using the workqueue.
>>
>> Ok, I'll add comment if we keep using the workqueue.
>
>Maybe do that for getting the new bitmap code in ASAP and then
>revisit the above separately?
>
>
Sure, sorry that I am in a business travel suddenly. I will get back to
this ASAP I return.
Thanks
Kuai
Powered by blists - more mailing lists