From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: linux-xfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] xfs: fix inobt inode allocation search optimization
Date: Fri, 11 Aug 2017 08:59:56 -0700 [thread overview]
Message-ID: <20170811155956.GZ24087@magnolia> (raw)
In-Reply-To: <a605146bb4b492462c44a5c8697533a40b9f57bb.1502426715.git.osandov@fb.com>
On Thu, Aug 10, 2017 at 09:45:45PM -0700, Omar Sandoval wrote:
Looks ok, will test...
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> From: Omar Sandoval <osandov@fb.com>
>
> When we try to allocate a free inode by searching the inobt, we try to
> find the inode nearest the parent inode by searching chunks both left
> and right of the chunk containing the parent. As an optimization, we
> cache the leftmost and rightmost records that we previously searched; if
> we do another allocation with the same parent inode, we'll pick up the
> search where it last left off.
>
> There's a bug in the case where we found a free inode to the left of the
> parent's chunk: we need to update the cached left and right records, but
> because we already reassigned the right record to point to the left, we
> end up assigning the left record to both the cached left and right
> records.
>
> This isn't a correctness problem strictly, but it can result in the next
> allocation rechecking chunks unnecessarily or allocating inodes further
> away from the parent than it needs to. Fix it by swapping the record
> pointer after we update the cached left and right records.
>
> Fixes: bd169565993b ("xfs: speed up free inode search")
> Signed-off-by: Omar Sandoval <osandov@fb.com>
> ---
> fs/xfs/libxfs/xfs_ialloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/xfs/libxfs/xfs_ialloc.c b/fs/xfs/libxfs/xfs_ialloc.c
> index ffd5a15d1bb6..abf5beaae907 100644
> --- a/fs/xfs/libxfs/xfs_ialloc.c
> +++ b/fs/xfs/libxfs/xfs_ialloc.c
> @@ -1246,13 +1246,13 @@ xfs_dialloc_ag_inobt(
>
> /* free inodes to the left? */
> if (useleft && trec.ir_freecount) {
> - rec = trec;
> xfs_btree_del_cursor(cur, XFS_BTREE_NOERROR);
> cur = tcur;
>
> pag->pagl_leftrec = trec.ir_startino;
> pag->pagl_rightrec = rec.ir_startino;
> pag->pagl_pagino = pagino;
> + rec = trec;
> goto alloc_inode;
> }
>
> --
> 2.14.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-08-11 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 4:45 [PATCH] xfs: fix inobt inode allocation search optimization Omar Sandoval
2017-08-11 11:23 ` Christoph Hellwig
2017-08-11 15:59 ` Darrick J. Wong [this message]
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=20170811155956.GZ24087@magnolia \
--to=darrick.wong@oracle.com \
--cc=kernel-team@fb.com \
--cc=linux-xfs@vger.kernel.org \
--cc=osandov@osandov.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