From: Luis Chamberlain <mcgrof@kernel.org>
To: linux-fsdevel@vger.kernel.org
Cc: linux-block@vger.kernel.org, linux-mm@kvack.org,
Hannes Reinecke <hare@suse.de>,
Pankaj Raghav <p.raghav@samsung.com>,
Daniel Gomez <da.gomez@samsung.com>,
mcgrof@kernel.org
Subject: Large Block Sizes update and monthly sync ups
Date: Thu, 12 Oct 2023 10:56:24 -0700 [thread overview]
Message-ID: <ZSgzSPAF8VpC9PPD@bombadil.infradead.org> (raw)
Folks working on LBS met up at this year's ALPSS 2023 conference and
we have started to put effort to merge our efforts together so that the
next patch iteration is done in coordination as a group effort. The first
order of work is to merge the minorder stuff on the page cache with its
respective huge set of testing requirements. In parallel other work can go.
There has been enough interest in this topic, so to this end top help sync
with folks we're going to be putting together a monthly sync up where we can
review progress, blockers, questions, and next steps before we post the next
patch series.
The first sync up will take place on Halloween October 31st 2023 at
5pm CEST / 8 am PST. If you're in Asia we apologize in advance, but
given at least one person's expressed interest in that region in the
future we could pivot the next meeting to acomodate that time zone and
then alternatate every other month so we all suffer equally.
This sync up will take place over zoom, if you'd like to attend please
let me know and I'll add you to the calendar invite.
Luis
reply other threads:[~2023-10-12 17:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZSgzSPAF8VpC9PPD@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=da.gomez@samsung.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=p.raghav@samsung.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