[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c8b65567-6a4d-2e61-b2a0-3a757ae9b36c@paragon-software.com>
Date: Wed, 13 Jul 2022 19:41:58 +0300
From: Konstantin Komarov <almaz.alexandrovich@...agon-software.com>
To: Christoph Hellwig <hch@...radead.org>
CC: <ntfs3@...ts.linux.dev>, <linux-kernel@...r.kernel.org>,
<linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 0/2] fs/ntfs3: Refactoring and improving logic in run_pack
On 7/7/22 07:42, Christoph Hellwig wrote:
> Hi Konstantin,
>
> now that you have time to actively work on the ntfs3 driver again, can
> you consider looking into converting the I/O path to iomap, as already
> request during the merge? Getting drivers off the old buffer head based
> I/O helpers is something we need to address in the coming years, so
> any relatively simple and actually maintained file system would be a
> good start.
>
> On Wed, Jul 06, 2022 at 08:31:25PM +0300, Konstantin Komarov wrote:
>> 2 patches:
>> - some comments and making function static;
>> - improving speed of run_pack by checking runs in advance
>>
>> Konstantin Komarov (2):
>> fs/ntfs3: Added comments to frecord functions
>> fs/ntfs3: Check possible errors in run_pack in advance
>>
>> fs/ntfs3/bitmap.c | 3 +--
>> fs/ntfs3/frecord.c | 8 ++++----
>> fs/ntfs3/ntfs_fs.h | 1 -
>> fs/ntfs3/run.c | 41 +++++++++++++++++++++++------------------
>> 4 files changed, 28 insertions(+), 25 deletions(-)
>>
>> --
>> 2.37.0
>>
> ---end quoted text---
Hi Christoph
I will look into converting the I/O path to iomap.
Thank you for reminding about it.
Powered by blists - more mailing lists