linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kmo@daterainc.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org
Subject: [GIT PULL] bcache changes for 3.15
Date: Tue, 18 Mar 2014 12:56:03 -0700	[thread overview]
Message-ID: <20140318195603.GI11655@kmo> (raw)

Jens, here's the bcache changes for 3.15. Lots of bugfixes, and some refactoring
and cleanups.

The following changes since commit 6d0abeca3242a88cab8232e4acd7e2bf088f3bc2:

  Linux 3.14-rc3 (2014-02-16 13:30:25 -0800)

are available in the git repository at:

  git://evilpiepirate.org/~kent/linux-bcache.git bcache-for-3.15

for you to fetch changes up to cb85114956dc88b287afca2872658f562acbc302:

  bcache: remove nested function usage (2014-03-18 12:39:28 -0700)

----------------------------------------------------------------
John Sheu (1):
      bcache: remove nested function usage

Kent Overstreet (21):
      bcache: Fix another compiler warning on m68k
      bcache: Fix flash_dev_cache_miss() for real this time
      bcache: Fix a shutdown bug
      bcache: Fix a lockdep splat in an error path
      bcache: Fix a null ptr deref in journal replay
      bcache: Fix a journalling reclaim after recovery bug
      bcache: Fix a bug recovering from unclean shutdown
      bcache: Fix another bug recovering from unclean shutdown
      bcache: Fix discard granularity
      bcache: Fix moving_pred()
      bcache: Kill dead cgroup code
      bcache: Better alloc tracepoints
      bcache: Improve priority_stats
      bcache: Add bch_keylist_init_single()
      bcache: Add a real GC_MARK_RECLAIMABLE
      bcache: Fix a race when freeing btree nodes
      bcache: btree locking rework
      bcache: Kill btree_io_wq
      bcache: Rework btree cache reserve handling
      bcache: Kill unused freelist
      bcache: Kill bucket->gc_gen

Nicholas Swenson (2):
      bcache: Fix moving_gc deadlocking with a foreground write
      bcache: stop moving_gc marking buckets that can't be moved.

 drivers/md/bcache/Kconfig     |   8 -
 drivers/md/bcache/alloc.c     | 173 +++++-------
 drivers/md/bcache/bcache.h    |  56 ++--
 drivers/md/bcache/bset.c      |   4 +-
 drivers/md/bcache/bset.h      |   6 +
 drivers/md/bcache/btree.c     | 592 ++++++++++++++++++++++++------------------
 drivers/md/bcache/btree.h     |  12 +-
 drivers/md/bcache/extents.c   |  36 +--
 drivers/md/bcache/journal.c   |  46 ++--
 drivers/md/bcache/journal.h   |   1 +
 drivers/md/bcache/movinggc.c  |  18 +-
 drivers/md/bcache/request.c   | 201 +-------------
 drivers/md/bcache/request.h   |  19 +-
 drivers/md/bcache/stats.c     |   3 -
 drivers/md/bcache/super.c     |  64 ++---
 drivers/md/bcache/sysfs.c     | 155 ++++++-----
 drivers/md/bcache/trace.c     |   2 +-
 include/trace/events/bcache.h |  52 ++--
 18 files changed, 664 insertions(+), 784 deletions(-)

             reply	other threads:[~2014-03-18 19:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 19:56 Kent Overstreet [this message]
2014-03-19 14:35 ` [GIT PULL] bcache changes for 3.15 Jens Axboe

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=20140318195603.GI11655@kmo \
    --to=kmo@daterainc.com \
    --cc=axboe@kernel.dk \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).