From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: Next btrfs development cycle - 5.8
Date: Mon, 16 Mar 2020 23:38:19 +0100 [thread overview]
Message-ID: <20200316223819.13329-1-dsterba@suse.com> (raw)
From: David Sterba <dsterba@suse.cz>
Hi,
a friendly reminder of the timetable and what's expected at this phase.
5.5 - current
5.6 - upcoming, urgent regression fixes only
5.7 - development closed, pull request in prep, fixes or regressions only
5.8 - development open, until 5.7-rc5 (at least)
(https://btrfs.wiki.kernel.org/index.php/Developer%27s_FAQ#Development_schedule)
Current status
--------------
Short summary of patch groups:
* per-inode file extent tree
* SRCU root protection replaced by reference counting
* leak detector for root in-memory structures
* per-transaction pinned extents
* buffer heads replaced by bios for super block reading
* backref resolution speedup
* v2 ioctl for subvolume deletion (delete by id possible)
* DREW lock (double reader/writer exclusion lock) abstracted from subvolume
writer vs NOCOW
* support reflink/clone of inline files
* more cancellation points for relocation
* make ranged full fsyncs more efficient
* several relocation fixes
* removal of deprecated async subvolume creation mode
Cleanups:
* submit extent pages
* sysfs handlers
* uuid wrappers
* chunk allocation (in preparation for zoned allocator)
+ many other fixes
There are 200+ patches, but I'm more worried about possible interactions
between the various parts that got changed. Misc-next should be in a good
shape but stress testing could reveal some corner cases. There are changes in
independent areas same as core building blocks.
Merge outlook
-------------
From now on only selected fixes will be merged so 5.7 queue is effectively
frozen. The merge window will probably open next week, and if not I don't want
to do any risky changes.
With the flood of new patchsets in the mailinglist the 5.8 round will start
soonish. As in the previous development cycle, the order of patches is roughly
this
1. fixes, minor cleanups
2. fixes that need refactoring or cleanups
3. small-sized features, with acked interface
4. the rest (big features, intrusive core changes, ...)
Git development repos
---------------------
k.org: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git
devel1: https://gitlab.com/kdave/btrfs-devel
devel2: https://github.com/kdave/btrfs-devel
reply other threads:[~2020-03-16 22:38 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=20200316223819.13329-1-dsterba@suse.com \
--to=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).