From: Christoph Hellwig <hch@infradead.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Dave Chinner <david@fromorbit.com>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Aravinda Herle <araherle@in.ibm.com>
Subject: Re: [RFCv2 2/3] iomap: Change uptodate variable name to state
Date: Tue, 31 Jan 2023 07:07:01 -0800 [thread overview]
Message-ID: <Y9kulWxXxcYye09a@infradead.org> (raw)
In-Reply-To: <Y9hDu8hVBa3qJTNw@casper.infradead.org>
On Mon, Jan 30, 2023 at 10:24:59PM +0000, Matthew Wilcox wrote:
> > a single bitmap of undefined length, then change the declaration and
> > the structure size calculation away from using array notation and
> > instead just use pointers to the individual bitmap regions within
> > the allocated region.
>
> Hard to stomach that solution when the bitmap is usually 2 bytes long
> (in Ritesh's case). Let's see a version of this patchset with
> accessors before rendering judgement.
Yes. I think what we need is proper helpers that are self-documenting
for every bitmap update as I already suggsted last round. That keeps
the efficient allocation, and keeps all the users self-documenting.
It just adds a bit of boilerplate for all these helpers, but that
should be worth having the clarity and performance benefits.
next prev parent reply other threads:[~2023-01-31 15:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 16:14 [RFCv2 0/3] iomap: Add support for subpage dirty state tracking to improve write performance Ritesh Harjani (IBM)
2023-01-30 16:14 ` [RFCv2 1/3] iomap: Move creation of iomap_page early in __iomap_write_begin Ritesh Harjani (IBM)
2023-01-30 17:02 ` Christoph Hellwig
2023-01-30 20:21 ` Ritesh Harjani (IBM)
2023-01-30 21:00 ` Matthew Wilcox
2023-01-31 18:37 ` Ritesh Harjani (IBM)
2023-01-31 18:48 ` Matthew Wilcox
2023-01-31 20:00 ` Ritesh Harjani (IBM)
2023-01-30 16:14 ` [RFCv2 2/3] iomap: Change uptodate variable name to state Ritesh Harjani (IBM)
2023-01-30 21:56 ` Dave Chinner
2023-01-30 22:24 ` Matthew Wilcox
2023-01-31 15:07 ` Christoph Hellwig [this message]
2023-01-31 18:05 ` Ritesh Harjani (IBM)
2023-01-30 16:14 ` [RFCv2 3/3] iomap: Support subpage size dirty tracking to improve write performance Ritesh Harjani (IBM)
2023-01-30 17:16 ` Christoph Hellwig
2023-01-30 18:01 ` Matthew Wilcox
2023-01-30 20:44 ` Ritesh Harjani (IBM)
2023-01-30 20:27 ` Ritesh Harjani (IBM)
2023-01-30 17:54 ` Matthew Wilcox
2023-01-30 20:34 ` Ritesh Harjani (IBM)
2023-01-30 18:10 ` [RFCv2 0/3] iomap: Add support for subpage dirty state " Matthew Wilcox
2023-01-30 21:01 ` Ritesh Harjani (IBM)
2023-02-02 4:45 ` Ritesh Harjani (IBM)
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=Y9kulWxXxcYye09a@infradead.org \
--to=hch@infradead.org \
--cc=araherle@in.ibm.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=willy@infradead.org \
/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