All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] block fixes for 2.6.39-rc3
Date: Mon, 18 Apr 2011 22:00:54 +0200	[thread overview]
Message-ID: <4DAC9876.6020004@fusionio.com> (raw)

Hi Linus,

With this in, I believe the only regression there's left is the one in
IDE which seems to be due to endless media events being generated. In
this round:

- Removal of the ->unplugged_fn(), as MD could not really use it. This
  adds a callback list instead, which MD can use to get notification on
  the level it requires.

- Neils MD fixes to fix with write intent bitmap hanging.

- Small fixup to use kblockd workqueue for the delay work, that was an
  oversight (it used the system workqueue instead).

- Small improvement to drop the queue lock before doing the async
  kblockd wakeup.

Please pull.

  git://git.kernel.dk/linux-2.6-block.git for-linus

Christoph Hellwig (1):
      block: add blk_run_queue_async

Jens Axboe (3):
      Revert "block: add callback function for unplug notification"
      block: drop queue lock before calling __blk_run_queue() for kblockd punt
      block: blk_delay_queue() should use kblockd workqueue

NeilBrown (7):
      block: Enhance new plugging support to support general callbacks
      md: use new plugging interface for RAID IO.
      md/dm - remove remains of plug_fn callback.
      md - remove old plugging code.
      md: provide generic support for handling unplug callbacks.
      md: incorporate new plugging into raid5.
      md: fix up raid1/raid10 unplugging.

 block/blk-core.c                 |   83 ++++++++++++++++++++++++++++--------
 block/blk-exec.c                 |    2 +-
 block/blk-flush.c                |    4 +-
 block/blk-settings.c             |   16 -------
 block/blk.h                      |    1 +
 block/cfq-iosched.c              |    6 +-
 block/elevator.c                 |    4 +-
 drivers/md/dm-raid.c             |    8 ----
 drivers/md/md.c                  |   87 ++++++++++++++++++++------------------
 drivers/md/md.h                  |   26 ++----------
 drivers/md/raid1.c               |   29 ++++++-------
 drivers/md/raid10.c              |   27 ++++++------
 drivers/md/raid5.c               |   61 +++++++++++---------------
 drivers/md/raid5.h               |    2 -
 drivers/scsi/scsi_lib.c          |    2 +-
 drivers/scsi/scsi_transport_fc.c |    2 +-
 include/linux/blkdev.h           |   12 +++--
 include/linux/device-mapper.h    |    1 -
 18 files changed, 186 insertions(+), 187 deletions(-)

-- 
Jens Axboe


                 reply	other threads:[~2011-04-18 20:01 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=4DAC9876.6020004@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.