Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Simon Kirby <sim@hostway.ca>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
	Josef Bacik <josef@redhat.com>
Subject: Re: Hot rb_next, setup_cluster_no_bitmap
Date: Wed, 03 Aug 2011 21:13:26 -0400	[thread overview]
Message-ID: <1312420323-sup-5706@shiny> (raw)
In-Reply-To: <20110803231059.GB20056@hostway.ca>

Excerpts from Simon Kirby's message of 2011-08-03 19:10:59 -0400:
> On Wed, Aug 03, 2011 at 03:39:49PM -0700, Simon Kirby wrote:
> 
> > On Wed, Aug 03, 2011 at 03:06:55PM -0700, Simon Kirby wrote:
> > 
> > > I see Josef's 86d4a77ba3dc4ace238a0556541a41df2bd71d49 introduced the
> > > bitmaps list. I could try temporarily reverting this (some fixups needed)
> > > if anybody thinks my cache bouncing idea might be slightly possible.
> > 
> > I'll try the attached and see how the profile changes.
> 
> Hmm, I bound the SMP affinity of all of the btrfs processes to one CPU,
> and the page dirtying rate got slower, so I suspect the writes aren't
> really a big deal, and the problem is just that there is way too much
> walking going on after rsync has ran for a while and loads everything
> into memory.
> 
> Any ideas?

The current for-linus branch gets rid of all the bottlenecks in the
metadata blocks.  So now we're stuck with the bottlenecks in the
allocator.

There are a few simple things we can do here but Josef has a patch that
fixes delalloc reservations for inline extents that might help as a
first step.

-chris

  reply	other threads:[~2011-08-04  1:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 22:06 Hot rb_next, setup_cluster_no_bitmap Simon Kirby
2011-08-03 22:39 ` Simon Kirby
2011-08-03 23:10   ` Simon Kirby
2011-08-04  1:13     ` Chris Mason [this message]
2011-08-04  1:32     ` Simon Kirby
2011-08-04 14:04       ` Chris Mason
2011-08-04 17:28         ` Simon Kirby

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=1312420323-sup-5706@shiny \
    --to=chris.mason@oracle.com \
    --cc=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sim@hostway.ca \
    /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