public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Brian Foster <bfoster@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: use per-AG reservations for the finobt
Date: Tue, 24 Jan 2017 10:27:17 -0800	[thread overview]
Message-ID: <20170124182717.GD9134@birch.djwong.org> (raw)
In-Reply-To: <20170124161917.GF60234@bfoster.bfoster>

On Tue, Jan 24, 2017 at 11:19:18AM -0500, Brian Foster wrote:
> 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..

<anecdote>

So on this laptop, we have:

$ df -i /storage/; df /storage/
Filesystem                     Inodes IUsed IFree IUse% Mounted on
/dev/mapper/birch_disk-storage   466M  1.8M  464M    1% /storage
Filesystem                      Size  Used Avail Use% Mounted on
/dev/mapper/birch_disk-storage  931G  525G  407G  57% /storage

$ sudo xfs_io -c 'fsmap -v -n 1024' . | grep 'inode btree' | \
	awk '{moo[$6] += $8}END{for (x=0;x<=255;x++) if (x in moo) print x, moo[x]}'
0	144
1	160
2	152
3	136
4	152
5	152
6	168
7	152

So on average we have ~160 sectors (or about 20 blocks) of inobt/finobt
in each of 8 AGs.

</anecdote>

--D

> 
> 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
> --
> 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

      reply	other threads:[~2017-01-24 18:27 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
2017-01-24 18:27       ` 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=20170124182717.GD9134@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox