From: Anuj Gupta <anuj20.g@samsung.com>
To: Jan Kara <jack@suse.cz>
Cc: Kundan Kumar <kundan.kumar@samsung.com>,
Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@lst.de>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
mcgrof@kernel.org, joshi.k@samsung.com, axboe@kernel.dk,
clm@meta.com, willy@infradead.org, gost.dev@samsung.com
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] Parallelizing filesystem writeback
Date: Thu, 20 Mar 2025 12:38:18 +0530 [thread overview]
Message-ID: <20250320070818.GB16509@green245> (raw)
In-Reply-To: <gamxtewl5yzg4xwu7lpp7obhp44xh344swvvf7tmbiknvbd3ww@jowphz4h4zmb>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
> I think xarray here is overkill. I'd just make this a plain array:
>
> struct bdi_writeback_ctx **bdi_wb_ctx_arr;
>
> which will get allocated with nr_wb_ctx entries during bdi_init(). Also I'd
> make default_ctx just be entry at index 0 in this array. I'm undecided
> whether it will be clearer to just drop default_ctx altogether or keep it
> and set:
>
> struct bdi_writeback_ctx *default_ctx = bdi_wb_ctx_arr[0];
>
> on init so I'll leave that up to you.
Killing default_ctx completely seems like a better choice here. This
allows us to unconditionally use the for_each_bdi_wb_ctx loop, even for
the existing single writeback case, by simply relying on bdi_wb_ctx[0].
It also eliminates the need for is_parallel, simplifying the design.
Thanks for the detailed review, Jan! Your suggestions look good to me
and help streamline the plumbing. I'll incorporate them in the next
version.
Thanks,
Anuj Gupta
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2025-03-20 11:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250129103448epcas5p1f7d71506e4443429a0b0002eb842e749@epcas5p1.samsung.com>
2025-01-29 10:26 ` [LSF/MM/BPF TOPIC] Parallelizing filesystem writeback Kundan Kumar
2025-01-29 15:42 ` Christoph Hellwig
2025-01-31 9:57 ` Kundan Kumar
2025-01-29 22:51 ` Dave Chinner
2025-01-31 9:32 ` Kundan Kumar
2025-01-31 17:06 ` Luis Chamberlain
2025-02-04 2:50 ` Dave Chinner
2025-02-04 5:06 ` Christoph Hellwig
2025-02-04 7:08 ` Dave Chinner
2025-02-10 17:28 ` [Lsf-pc] " Jan Kara
2025-02-11 1:13 ` Dave Chinner
2025-02-11 13:43 ` Jan Kara
2025-02-20 14:19 ` Kundan Kumar
2025-03-13 20:22 ` Jan Kara
2025-03-18 3:42 ` Dave Chinner
2025-03-19 8:07 ` Anuj Gupta
2025-03-18 6:41 ` Kundan Kumar
2025-03-18 11:37 ` Anuj Gupta
2025-03-19 15:54 ` Jan Kara
2025-03-20 7:08 ` Anuj Gupta [this message]
2025-03-12 17:47 ` Luis Chamberlain
2025-03-13 19:39 ` Jan Kara
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=20250320070818.GB16509@green245 \
--to=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=clm@meta.com \
--cc=david@fromorbit.com \
--cc=gost.dev@samsung.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=joshi.k@samsung.com \
--cc=kundan.kumar@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--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