public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Murphy Zhou <jencce.kernel@gmail.com>,
	linux-xfs@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: A NFS, xfs, reflink and rmapbt story
Date: Mon, 27 Jan 2020 17:36:31 -0500	[thread overview]
Message-ID: <20200127223631.GA28982@fieldses.org> (raw)
In-Reply-To: <20200124011019.GA8247@magnolia>

On Thu, Jan 23, 2020 at 05:10:19PM -0800, Darrick J. Wong wrote:
> On Thu, Jan 23, 2020 at 04:32:17PM +0800, Murphy Zhou wrote:
> > Hi,
> > 
> > Deleting the files left by generic/175 costs too much time when testing
> > on NFSv4.2 exporting xfs with rmapbt=1.
> > 
> > "./check -nfs generic/175 generic/176" should reproduce it.
> > 
> > My test bed is a 16c8G vm.
> 
> What kind of storage?
> 
> > NFSv4.2  rmapbt=1   24h+
> 
> <URK> Wow.  I wonder what about NFS makes us so slow now?  Synchronous
> transactions on the inactivation?  (speculates wildly at the end of the
> workday)
> 
> I'll have a look in the morning.  It might take me a while to remember
> how to set up NFS42 :)

It may just be the default on a recent enough distro.

Though I'd be a little surprised if this behavior is specific to the
protocol version.

nfsd_unlink() is basically just vfs_unlink() followed by
commit_metadata().

--b.

> 
> --D
> 
> > NFSv4.2  rmapbt=0   1h-2h
> > xfs      rmapbt=1   10m+
> > 
> > At first I thought it hung, turns out it was just slow when deleting
> > 2 massive reflined files.
> > 
> > It's reproducible using latest Linus tree, and Darrick's deferred-inactivation
> > branch. Run latest for-next branch xfsprogs.
> > 
> > I'm not sure it's something wrong, just sharing with you guys. I don't
> > remember I have identified this as a regression. It should be there for
> > a long time.
> > 
> > Sending to xfs and nfs because it looks like all related. :)
> > 
> > This almost gets lost in my list. Not much information recorded, some
> > trace-cmd outputs for your info. It's easy to reproduce. If it's
> > interesting to you and need any info, feel free to ask.
> > 
> > Thanks,
> > 
> > 
> > 7)   0.279 us    |  xfs_btree_get_block [xfs]();
> > 7)   0.303 us    |  xfs_btree_rec_offset [xfs]();
> > 7)   0.301 us    |  xfs_rmapbt_init_high_key_from_rec [xfs]();
> > 7)   0.356 us    |  xfs_rmapbt_diff_two_keys [xfs]();
> > 7)   0.305 us    |  xfs_rmapbt_init_key_from_rec [xfs]();
> > 7)   0.306 us    |  xfs_rmapbt_diff_two_keys [xfs]();
> > 7)               |  xfs_rmap_query_range_helper [xfs]() {
> > 7)   0.279 us    |    xfs_rmap_btrec_to_irec [xfs]();
> > 7)               |    xfs_rmap_lookup_le_range_helper [xfs]() {
> > 1)   0.786 us    |  _raw_spin_lock_irqsave();
> > 7)               |      /* xfs_rmap_lookup_le_range_candidate: dev 8:34 agno 2 agbno 6416 len 256 owner 67160161 offset 99284480 flags 0x0 */
> > 7)   0.506 us    |    }
> > 7)   1.680 us    |  }

  reply	other threads:[~2020-01-27 22:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23  8:32 A NFS, xfs, reflink and rmapbt story Murphy Zhou
2020-01-24  1:10 ` Darrick J. Wong
2020-01-27 22:36   ` J. Bruce Fields [this message]
2020-02-05  6:22     ` Murphy Zhou
2020-02-16  8:28     ` Murphy Zhou
2020-02-17  0:36       ` J. Bruce Fields
2020-01-27 23:56   ` Dave Chinner
2020-02-05  6:52     ` Murphy Zhou

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=20200127223631.GA28982@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=darrick.wong@oracle.com \
    --cc=jencce.kernel@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --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