From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: <ntfs3@lists.linux.dev>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>
Subject: [PATCH 0/2] fs/ntfs3: Refactoring and improving logic in run_pack
Date: Wed, 6 Jul 2022 20:31:25 +0300 [thread overview]
Message-ID: <d578fcbe-e1f7-ffc7-2535-52eecb271a01@paragon-software.com> (raw)
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
next reply other threads:[~2022-07-06 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 17:31 Konstantin Komarov [this message]
2022-07-06 17:32 ` [PATCH 1/2] fs/ntfs3: Added comments to frecord functions Konstantin Komarov
2022-07-06 17:33 ` [PATCH 2/2] fs/ntfs3: Check possible errors in run_pack in advance Konstantin Komarov
2022-07-07 4:42 ` [PATCH 0/2] fs/ntfs3: Refactoring and improving logic in run_pack Christoph Hellwig
2022-07-13 16:41 ` Konstantin Komarov
2022-07-14 4:24 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d578fcbe-e1f7-ffc7-2535-52eecb271a01@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox