From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Christian Brauner <brauner@kernel.org>,
lsf-pc@lists.linux-foundation.org, Jan Kara <jack@suse.cz>,
Amir Goldstein <amir73il@gmail.com>
Cc: Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Pankaj Raghav <pankaj.raghav@linux.dev>,
Andres Freund <andres@anarazel.de>,
djwong@kernel.org, john.g.garry@oracle.com, willy@infradead.org,
hch@lst.de, Luis Chamberlain <mcgrof@kernel.org>,
dchinner@redhat.com, Javier Gonzalez <javier.gonz@samsung.com>,
gost.dev@samsung.com, tytso@mit.edu, p.raghav@samsung.com,
vi.shah@samsung.com, linux-xfs@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] Buffered atomic writes
Date: Fri, 24 Apr 2026 06:32:03 +0530 [thread overview]
Message-ID: <wlxxrx10.ritesh.list@gmail.com> (raw)
In-Reply-To: <d0c4d95b-8064-4a7e-996d-7ad40eb4976b@linux.dev>
Hi Christian / LSF committee,
> The preliminary schedule is accessible here:
> https://docs.google.com/spreadsheets/d/1mGEdDrWskp7Ua91jGXzquQGinorcD58DAVXhOiRp2Gg/edit?gid=1852749899#gid=1852749899
> It just hasn't been liked on the website yet.
Thanks for sharing the preliminary schedule. We had a discuss about this
among us Me, Ojaswin, Pankaj and Andres too is on the same page.
We were thinking if it is possible to extend the Buffered Atomic Write
session into two "continuous" halves of 30mins each (total of 60mins)?
Looks like in the past couple of months, there has been some good
discussion & progress on this topic and we feel a 30min slot might not
be enough to cover everything, since we want to give more time for
QnA/Discussions.
This is how we were thinking it might go:
Buffered atomic write: Usecase & Discussion with Postgres
I think in this slot Pankaj and Andres would like to cover:
1. Buffered atomic write usecases
2. How Postgres would like to use it and why is it important for them, ...
3. Q&A/Discussion
@Pankaj / Andres - please add and/or correct if I missed anything in above.
Buffered atomic write: The writethrough approach
Ojaswin and I have been working on this and since a few approaches were
tried, before we landed on the writethrough model, we think this may
need a 30-minute slot of its own:
So, I think Ojaswin can cover the following in this slot:
1. Briefly cover the previous 2 approaches on buffered atomic writes and
what were the problems in those approaches.
2. Design of writethrough and its use beyond just support of buffered atomic
writes.
3. Performance concern with the current approach (not sure if we will be
able to get a thorough benchmarking numbers, but will try to share
some initial data at least)
4. Q&A/Discussion
Do you think this is possible? It will be best to keep both back to back,
so that buffered writethrough can be discussed in continuation.
-ritesh
next prev parent reply other threads:[~2026-04-24 4:28 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 10:20 [LSF/MM/BPF TOPIC] Buffered atomic writes Pankaj Raghav
2026-02-13 13:32 ` Ojaswin Mujoo
2026-02-16 9:52 ` Pankaj Raghav
2026-02-16 15:45 ` Andres Freund
2026-02-17 12:06 ` Jan Kara
2026-02-17 12:42 ` Pankaj Raghav
2026-02-17 16:21 ` Andres Freund
2026-02-18 1:04 ` Dave Chinner
2026-02-18 6:47 ` Christoph Hellwig
2026-02-18 23:42 ` Dave Chinner
2026-02-17 16:13 ` Andres Freund
2026-02-17 18:27 ` Ojaswin Mujoo
2026-02-17 18:42 ` Andres Freund
2026-02-18 17:37 ` Jan Kara
2026-02-18 21:04 ` Andres Freund
2026-02-19 0:32 ` Dave Chinner
2026-02-17 18:33 ` Ojaswin Mujoo
2026-02-17 17:20 ` Ojaswin Mujoo
2026-02-18 17:42 ` [Lsf-pc] " Jan Kara
2026-02-18 20:22 ` Ojaswin Mujoo
2026-02-16 11:38 ` Jan Kara
2026-02-16 13:18 ` Pankaj Raghav
2026-02-17 18:36 ` Ojaswin Mujoo
2026-02-16 15:57 ` Andres Freund
2026-02-17 18:39 ` Ojaswin Mujoo
2026-02-18 0:26 ` Dave Chinner
2026-02-18 6:49 ` Christoph Hellwig
2026-02-18 12:54 ` Ojaswin Mujoo
2026-02-15 9:01 ` Amir Goldstein
2026-02-17 5:51 ` Christoph Hellwig
2026-02-17 9:23 ` [Lsf-pc] " Amir Goldstein
2026-02-17 15:47 ` Andres Freund
2026-02-17 22:45 ` Dave Chinner
2026-02-18 4:10 ` Andres Freund
2026-02-18 6:53 ` Christoph Hellwig
2026-02-18 6:51 ` Christoph Hellwig
2026-02-20 10:08 ` Pankaj Raghav (Samsung)
2026-02-20 15:10 ` Christoph Hellwig
2026-02-24 13:09 ` Pankaj Raghav (Samsung)
2026-02-24 15:04 ` Christoph Hellwig
2026-04-24 1:02 ` Ritesh Harjani [this message]
2026-04-24 4:42 ` Matthew Wilcox
2026-04-24 4:50 ` Ritesh Harjani
2026-04-24 6:57 ` Amir Goldstein
2026-04-24 9:40 ` Ritesh Harjani
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=wlxxrx10.ritesh.list@gmail.com \
--to=ritesh.list@gmail.com \
--cc=amir73il@gmail.com \
--cc=andres@anarazel.de \
--cc=brauner@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=gost.dev@samsung.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=javier.gonz@samsung.com \
--cc=john.g.garry@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=p.raghav@samsung.com \
--cc=pankaj.raghav@linux.dev \
--cc=tytso@mit.edu \
--cc=vi.shah@samsung.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