public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>,
	Matthew Wilcox <willy@infradead.org>
Cc: Christian Brauner <brauner@kernel.org>,
	lsf-pc@lists.linux-foundation.org, Jan Kara <jack@suse.cz>,
	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, 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,
	"Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] Buffered atomic writes
Date: Fri, 24 Apr 2026 15:10:58 +0530	[thread overview]
Message-ID: <tst0snkl.ritesh.list@gmail.com> (raw)
In-Reply-To: <CAOQ4uxi0bTwj7oCWR1iOhqzPkB94cVgh=9Prh1kHxnObuLCz0g@mail.gmail.com>

Amir Goldstein <amir73il@gmail.com> writes:

> On Fri, Apr 24, 2026 at 7:07 AM Ritesh Harjani <ritesh.list@gmail.com> wrote:
>>
>> Matthew Wilcox <willy@infradead.org> writes:
>>
>> > On Fri, Apr 24, 2026 at 06:32:03AM +0530, Ritesh Harjani wrote:
>> >> We were thinking if it is possible to extend the Buffered Atomic Write
>> >> session into two "continuous" halves of 30mins each (total of 60mins)?
>> >
>> > This is painful because you've requested me, plus both Storage and FS.
>> > FS has lots of space, but I don't, and Storage is also pretty full.
>>
>> I see, sorry about making your (and PC) life difficult here. I know it's
>> a lot of planning :(
>>
>> I think, both FS+IO folks will be interested to discuss both of these
>> topics. Do you think breaking this into two discontiguous session help
>> us plan better maybe? In case if we don't have any continuous slot, then
>> maybe we can split those into two.
>>
>
> I scheduled the two sessions as you requested 9:30-10:30
> for FS+IO and moved Parallel Writeback to Wednesday
> across the MM CXL session.
>

Thanks Amir. Yes, I think this will be very helpful.


>> >
>> > Do you need me for the full hour or just half of it?
>>
>> Although I understand buffered writethrough is an FS related area, but I
>> am sure a new writethrough I/O path is an overlap for you in page cache
>> as well :)  So, yes, it will be good to have your feedback on the second
>> part of this discussion which is - buffered write-through for buffered
>> atomic writes.
>>
>
> Matthew,
>
> I don't know why Parallel Writeback was scheduled as an MM session,
> but if you think it should include MM, could you move the CXL session
> to the now free MM slot on Monday 9:30, so that we can extend
> Parallel Writeback into MM?
>
> This will allow you to participate in the atomic buffered write sessions.
>

Thanks again!

-ritesh

      reply	other threads:[~2026-04-24  9:43 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
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 [this message]

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=tst0snkl.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=vbabka@kernel.org \
    --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