From: "Theodore Ts'o" <tytso@mit.edu>
To: Ritesh Harjani <ritesh.list@gmail.com>
Cc: Jan Kara <jack@suse.cz>, John Garry <john.g.garry@oracle.com>,
djwong@kernel.org, Ojaswin Mujoo <ojaswin@linux.ibm.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH v5 0/7] ext4: Add multi-fsblock atomic write support with bigalloc
Date: Mon, 19 May 2025 11:47:54 -0400 [thread overview]
Message-ID: <20250519154754.GC38098@mit.edu> (raw)
In-Reply-To: <877c2cx69z.fsf@gmail.com>
On Mon, May 19, 2025 at 03:37:52PM +0530, Ritesh Harjani wrote:
>
> So, thanks for taking care of that. After looking at Zhang's series, I
> figured, we may need EXT4_EX_CACHE flag too in
> ext4_convert_unwritten_extents_atomic()....
>
> Other than adding the no cache flag, couple of other minor
> simplifications can be done too, I guess for e.g. simplifying the
> query_flags logic in ext4_map_query_blocks() function.
>
> So I am thinking maybe I will provide the above fix and few other minor
> simplfications which we could do on top of ext4's dev branch (after we
> rebased atomic write changes on top of Zhang's series). Please let me
> know if that is ok?
Sure, that would be great. Many thanks!!
- Ted
next prev parent reply other threads:[~2025-05-19 15:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 19:50 [PATCH v5 0/7] ext4: Add multi-fsblock atomic write support with bigalloc Ritesh Harjani (IBM)
2025-05-15 19:50 ` [PATCH v5 1/7] ext4: Document an edge case for overwrites Ritesh Harjani (IBM)
2025-05-15 19:50 ` [PATCH v5 2/7] ext4: Check if inode uses extents in ext4_inode_can_atomic_write() Ritesh Harjani (IBM)
2025-05-15 19:50 ` [PATCH v5 3/7] ext4: Make ext4_meta_trans_blocks() non-static for later use Ritesh Harjani (IBM)
2025-05-15 19:50 ` [PATCH v5 4/7] ext4: Add support for EXT4_GET_BLOCKS_QUERY_LEAF_BLOCKS Ritesh Harjani (IBM)
2025-05-15 19:50 ` [PATCH v5 5/7] ext4: Add multi-fsblock atomic write support with bigalloc Ritesh Harjani (IBM)
2025-05-15 19:50 ` [PATCH v5 6/7] ext4: Enable support for ext4 multi-fsblock atomic write using bigalloc Ritesh Harjani (IBM)
2025-05-15 19:50 ` [PATCH v5 7/7] ext4: Add atomic block write documentation Ritesh Harjani (IBM)
2025-05-16 8:55 ` John Garry
2025-05-16 12:19 ` Theodore Ts'o
2025-05-16 13:05 ` John Garry
2025-05-16 13:31 ` Carlos Maiolino
2025-05-16 14:48 ` Theodore Ts'o
2025-05-16 15:10 ` Darrick J. Wong
2025-05-16 18:13 ` Carlos Maiolino
2025-05-16 14:36 ` Ritesh Harjani
2025-05-16 14:15 ` Ritesh Harjani
2025-05-19 10:07 ` [PATCH v5 0/7] ext4: Add multi-fsblock atomic write support with bigalloc Ritesh Harjani
2025-05-19 15:47 ` Theodore Ts'o [this message]
2025-05-20 14:40 ` Theodore Ts'o
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=20250519154754.GC38098@mit.edu \
--to=tytso@mit.edu \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=john.g.garry@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.