]> git.ipfire.org Git - thirdparty/xfsprogs-dev.git/commitdiff
xfs: extsize hints are not unlikely in xfs_bmap_btalloc
authorChristoph Hellwig <hch@lst.de>
Thu, 16 Feb 2017 03:04:03 +0000 (21:04 -0600)
committerEric Sandeen <sandeen@redhat.com>
Thu, 16 Feb 2017 03:04:03 +0000 (21:04 -0600)
Source kernel commit: 493611ebd62673f39e2f52c2561182c558a21cb6

With COW files they are the hotpath, just like for files with the
extent size hint attribute.  We really shouldn't micro-manage anything
but failure cases with unlikely.

Additionally Arnd Bergmann recently reported that one of these two
unlikely annotations causes link failures together with an upcoming
kernel instrumentation patch, so let's get rid of it ASAP.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reported-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
libxfs/xfs_bmap.c

index 1b8d61ea5ce47148f27a0ec11ed81857f39eee6d..00945488154e8adbeaad9b6f1275e6e54bd9aebe 100644 (file)
@@ -3620,7 +3620,7 @@ xfs_bmap_btalloc(
                align = xfs_get_cowextsz_hint(ap->ip);
        else if (xfs_alloc_is_userdata(ap->datatype))
                align = xfs_get_extsz_hint(ap->ip);
-       if (unlikely(align)) {
+       if (align) {
                error = xfs_bmap_extsize_align(mp, &ap->got, &ap->prev,
                                                align, 0, ap->eof, 0, ap->conv,
                                                &ap->offset, &ap->length);
@@ -3692,7 +3692,7 @@ xfs_bmap_btalloc(
                args.minlen = ap->minlen;
        }
        /* apply extent size hints if obtained earlier */
-       if (unlikely(align)) {
+       if (align) {
                args.prod = align;
                if ((args.mod = (xfs_extlen_t)do_mod(ap->offset, args.prod)))
                        args.mod = (xfs_extlen_t)(args.prod - args.mod);