[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <10485bcf-5ccf-4fec-b403-0d895236c131@163.com>
Date: Tue, 19 Aug 2025 20:22:42 +0800
From: Chi Zhiling <chizhiling@....com>
To: Matthew Wilcox <willy@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
Namjae Jeon <linkinjeon@...nel.org>, Sungjong Seo <sj1557.seo@...sung.com>,
Yuezhang Mo <yuezhang.mo@...y.com>, Chi Zhiling <chizhiling@...inos.cn>
Subject: Re: [PATCH 1/3] mpage: terminate read-ahead on read error
On 2025/8/18 22:33, Matthew Wilcox wrote:
> On Mon, Aug 18, 2025 at 06:04:23PM +0800, Chi Zhiling wrote:
>>> Also, boy this is old code. Basically akpm code from pre-git times.
>>> It was quite innovative back then, but everybody who understood it has
>>> since moved on, got senile or probably died. Oh well.
>>
>> Actually, I think this patch is safe, but I'm not sure if we should fix this
>> issue. After all, this code has existed for a long time, and it's quite rare
>> to unplug the device during a copy operation :)
>
> Converting exfat to use iomap would be a valuable piece of work ...
Yes, this is indeed worthwhile, and exFAT should also be restructured to
support extents rather than fetching entries one by one.
I estimate this would bring significant performance improvements
Thanks,
Chi Zhiling
Powered by blists - more mailing lists