From: Dave Chinner <david@fromorbit.com>
To: John Garry <john.g.garry@oracle.com>
Cc: linux-xfs@vger.kernel.org, ojaswin@linux.ibm.com, ritesh.list@gmail.com
Subject: Re: [RFC PATCH 0/3] xfs: forced extent alignment
Date: Thu, 7 Mar 2024 07:54:23 +1100 [thread overview]
Message-ID: <ZejX/7Eqef7nZ6C7@dread.disaster.area> (raw)
In-Reply-To: <53f4519a-6798-4925-ad5a-5d2d17b6a00f@oracle.com>
On Wed, Mar 06, 2024 at 11:46:38AM +0000, John Garry wrote:
> On 06/03/2024 05:20, Dave Chinner wrote:
> > Hi Garry,
> >
> > I figured that it was simpler just to write the forced extent
> > alignment allocator patches that to make you struggle through them
> > and require lots of round trips to understand all the weird corner
> > cases.
>
> I appreciate that.
>
> >
> > The following 3 patches:
> >
> > - rework the setup and extent allocation logic a bit to make force
> > aligned allocation much easier to implement and understand
> > - move all the alignment adjustments into the setup logic
> > - rework the alignment slop calculations and greatly simplify the
> > the exact EOF block allocation case
> > - add a XFS_ALLOC_FORCEALIGN flag so that the inode config only
> > needs to be checked once at setup. This also allows other
> > allocation types (e.g. inode clusters) use forced alignment
> > allocation semantics in future.
> > - clearly document when we are turning off allocation alignment and
> > abort FORCEALIGN allocation at that point rather than doing
> > unaligned allocation.
> >
> > I've run this through fstests once so it doesn't let the smoke out,
> > but I haven't actually tested it against a stripe aligned filesystem
> > config yet, nor tested the forcealign functionality so it may not be
> > exactly right yet.
> >
> > Is this sufficiently complete for you to take from here into the
> > forcealign series?
> >
>
> I'll try it out.
>
> What baseline are these against? Mine were against v6.8-rc5, but I guess
> that you develop against an XFS integration tree. Maybe they apply and build
> cleanly against v6.8-rc5 ...
6.8-rc7 + linux-xfs/for-next + some other local patches to other
parts of XFS that shouldn't overlap with this patch set. I don't
think there's anything in for-next overlapping this code, so it
might just apply cleanly to your tree....
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2024-03-06 20:54 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:04 [PATCH v2 00/14] block atomic writes for XFS John Garry
2024-03-04 13:04 ` [PATCH v2 01/14] block: Add blk_validate_atomic_write_op_size() John Garry
2024-03-04 13:04 ` [PATCH v2 02/14] fs: xfs: Don't use low-space allocator for alignment > 1 John Garry
2024-03-04 22:15 ` Dave Chinner
2024-03-05 13:36 ` John Garry
2024-03-04 13:04 ` [PATCH v2 03/14] fs: xfs: Introduce FORCEALIGN inode flag John Garry
2024-03-04 13:04 ` [PATCH v2 04/14] fs: xfs: Make file data allocations observe the 'forcealign' flag John Garry
2024-03-05 0:44 ` Dave Chinner
2024-03-05 15:22 ` John Garry
2024-03-05 22:18 ` Dave Chinner
2024-03-06 5:20 ` [RFC PATCH 0/3] xfs: forced extent alignment Dave Chinner
2024-03-06 5:20 ` [PATCH 1/3] xfs: simplify extent allocation alignment Dave Chinner
2024-03-13 11:03 ` John Garry
2024-03-20 4:35 ` Dave Chinner
2024-03-26 16:08 ` John Garry
2024-04-02 5:58 ` Dave Chinner
2024-04-02 7:49 ` John Garry
2024-04-02 15:11 ` John Garry
2024-04-02 21:26 ` Dave Chinner
2024-04-03 8:49 ` John Garry
2024-04-02 23:44 ` Dave Chinner
2024-04-03 11:30 ` John Garry
2024-03-06 5:20 ` [PATCH 2/3] xfs: make EOF allocation simpler Dave Chinner
2024-03-06 5:20 ` [PATCH 3/3] xfs: introduce forced allocation alignment Dave Chinner
2024-03-06 11:46 ` [RFC PATCH 0/3] xfs: forced extent alignment John Garry
2024-03-06 17:52 ` John Garry
2024-03-06 20:54 ` Dave Chinner [this message]
2024-03-13 18:32 ` John Garry
2024-03-06 9:41 ` [PATCH v2 04/14] fs: xfs: Make file data allocations observe the 'forcealign' flag John Garry
2024-03-04 13:04 ` [PATCH v2 05/14] fs: xfs: Enable file data forcealign feature John Garry
2024-03-04 13:04 ` [PATCH v2 06/14] fs: xfs: Do not free EOF blocks for forcealign John Garry
2024-03-06 21:07 ` Dave Chinner
2024-03-07 11:38 ` John Garry
2024-03-04 13:04 ` [PATCH v2 07/14] fs: iomap: Sub-extent zeroing John Garry
2024-03-06 21:14 ` Dave Chinner
2024-03-07 11:51 ` John Garry
2024-03-04 13:04 ` [PATCH v2 08/14] fs: xfs: " John Garry
2024-03-06 22:00 ` Dave Chinner
2024-03-07 12:57 ` John Garry
2024-03-04 13:04 ` [PATCH v2 09/14] fs: Add FS_XFLAG_ATOMICWRITES flag John Garry
2024-03-04 13:04 ` [PATCH v2 10/14] fs: iomap: Atomic write support John Garry
2024-03-04 13:04 ` [PATCH v2 11/14] fs: xfs: Support FS_XFLAG_ATOMICWRITES for forcealign John Garry
2024-03-06 21:43 ` Dave Chinner
2024-03-07 12:42 ` John Garry
2024-03-04 13:04 ` [PATCH v2 12/14] fs: xfs: Support atomic write for statx John Garry
2024-03-06 21:31 ` Dave Chinner
2024-03-07 10:35 ` John Garry
2024-03-04 13:04 ` [PATCH v2 13/14] fs: xfs: Validate atomic writes John Garry
2024-03-06 21:22 ` Dave Chinner
2024-03-07 10:19 ` John Garry
2024-03-04 13:04 ` [PATCH v2 14/14] fs: xfs: Support setting FMODE_CAN_ATOMIC_WRITE John Garry
2024-03-06 21:33 ` Dave Chinner
2024-03-07 11:55 ` John Garry
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=ZejX/7Eqef7nZ6C7@dread.disaster.area \
--to=david@fromorbit.com \
--cc=john.g.garry@oracle.com \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox