From: Brian Foster <bfoster@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: use per-AG reservations for the finobt
Date: Tue, 24 Jan 2017 11:19:18 -0500 [thread overview]
Message-ID: <20170124161917.GF60234@bfoster.bfoster> (raw)
In-Reply-To: <20170124144937.GA27261@lst.de>
On Tue, Jan 24, 2017 at 03:49:37PM +0100, Christoph Hellwig wrote:
> On Tue, Jan 24, 2017 at 09:06:49AM -0500, Brian Foster wrote:
> > Darrick called out in the previous version that this requires traversal
> > of the entire tree at mount time. Do you have any test results on what
> > kind of worst case mount delays we could be looking at here?
>
> Even with pretty horribly fragmented file systems I've not seen
> major delays. But I don't have a setup with a lot of actual disks
> but mostly SSDs these days, so this might not statistically significant.
Heh, I might have some systems with slow storage around. ;P It may take
a little time to populate a large enough fs with inodes though..
Brian
> --
> 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
next prev parent reply other threads:[~2017-01-24 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 18:05 [PATCH v2] xfs: use per-AG reservations for the finobt Christoph Hellwig
2017-01-23 19:28 ` Darrick J. Wong
2017-01-24 14:02 ` Christoph Hellwig
2017-01-24 16:48 ` Darrick J. Wong
2017-01-24 19:50 ` Christoph Hellwig
2017-01-24 20:05 ` Darrick J. Wong
2017-01-24 14:06 ` Brian Foster
2017-01-24 14:49 ` Christoph Hellwig
2017-01-24 16:19 ` Brian Foster [this message]
2017-01-24 18:27 ` Darrick J. Wong
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=20170124161917.GF60234@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=hch@lst.de \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.