Sorry I find out that the CPU time regressions for btrfs are caused bysome additional trace events enabled on btrfs (for debugging anunrelated btrfs hang bug) which results in 7 times more trace eventlines: