All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: chris.mason@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: [GIT PULL] various updates for -rc3
Date: Tue, 15 Nov 2011 15:07:11 -0500	[thread overview]
Message-ID: <20111115200711.GC1944@localhost.localdomain> (raw)

Hey Chris,

Here are the cluster rework patches from Alexandre along with my tracepoints
patch and a couple of bugfixes.  This should fix the panics we've been seeing
when running xfstests 13 in a loop.  The cluster fixes I've been testing for a
while, and the tracepoints patch I used to profile the new clustering stuff to
make sure it was giving us a good behavior.  I have a repo with some tools to
use the allocator tracepoints

git://github.com/josefbacik/btrfs-tracing.git

In all respects Alexandre's patches work wonders.  You can pull from

git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-work.git for-chris

which is based off of your for-linus branch.  The shortlog and diffstat is
attached below.  Thanks,

Josef

Alexandre Oliva (3):
      Revamp btrfs cluster creation logic.
      Drop gap detection from btrfs.
      Require at least one extent of the requested size, but accept other smaller ones except when SSD_SPREAD is enabled.

Josef Bacik (3):
      Btrfs: add allocator tracepoints
      Btrfs: wait on caching if we're loading the free space cache
      Btrfs: clear pages dirty for io and set them extent mapped

 fs/btrfs/ctree.h             |    3 +-
 fs/btrfs/extent-tree.c       |  130 ++++++++++++++++++++++----------
 fs/btrfs/free-space-cache.c  |  130 ++++++++++++++++----------------
 include/trace/events/btrfs.h |  173 ++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 329 insertions(+), 107 deletions(-)

                 reply	other threads:[~2011-11-15 20:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20111115200711.GC1944@localhost.localdomain \
    --to=josef@redhat.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@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.