On 21/01/2020, 00:35, "linux-btrfs-owner@xxxxxxxxxxxxxxx on behalf of David Sterba" <linux-btrfs-owner@xxxxxxxxxxxxxxx on behalf of dsterba@xxxxxxxx> wrote:
CAUTION: This email originated from outside of Western Digital. Do not click on links or open attachments unless you recognize the sender and know that the content is safe.
From: David Sterba <dsterba@xxxxxxx>
Hi,
a friendly reminder of the timetable and what's expected at this phase.
5.4 - current
5.5 - upcoming, urgent regression fixes only
5.6 - development closed, pull request in prep, fixes or regressions only
5.7 - development open, until 5.5-rc6 (at least)
(https://btrfs.wiki.kernel.org/index.php/Developer%27s_FAQ#Development_schedule)
Current status
--------------
The amount of patches merged for 5.5 is heavily affected by the end of year
break, that is about 2 weeks long and the following week it takes to everybody
sync up again. So this is 3 less weeks of testing and I got the feeling that
everybody just dumped patches before going for the vacation. So the patch
backlog has grown again.
Current misc-next is reasonably stable, only selected fixes will be merged but
now it's effectively frozen. The merge window will probably open next week so
the timing is adequate.
Hilights of 5.6 changes
-----------------------
Async discard:
* an improved implementation of the -o discard, that leaves more time to freed
extents to coalesce to longer chunks that are more suitable for trimminng and
also limits the discard IO not to interfere with regular IO
* the current default IO submission rate should be good enough for most
usecases, but this might get tuned further, possibly adding some tunables if
required
Tree-checker got more b-tree leaf checks, and for location key for various
directory items.
Merge outlook
-------------
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, ...)
I do want to shake down the backlog, but please understand that it will be one
thing at a time, so it can be tested and reviewed. You don't have to ping or
resend. Wild ride ahead.
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
Hi David,
Is there any chance you can have a look at my Authenticated FS Patch(es) [1][2] for the 5.7 cycle?
Shall I re-send them re-based?
[1] https://lore.kernel.org/linux-btrfs/20191015121405.19066-1-jthumshirn@xxxxxxx/
[2] https://lore.kernel.org/linux-btrfs/20191016084158.7573-1-jthumshirn@xxxxxxx/
Thanks,
Johannes
