public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] block bits for 2.6.32-rc5
Date: Mon, 12 Oct 2009 11:48:03 +0200	[thread overview]
Message-ID: <20091012094803.GB9228@kernel.dk> (raw)


(Apologies to Linus who will receive this twice, I forgot to CC lkml
 when posting it).

Hi Linus,

This mostly contains a handful of fixes for CFQ. Nothing major, but bugs
none the less. There's also an improvement in the space stripping for
the io scheduler switching, making that behave more consistently. The
buggy read/write in_flight commit is back, this time behaving as it
should. And finally, two minor writeback changes from Wu using
io_schedule() in balance_dirty_pages() to get proper iowait accounting
(we did this in .31 and earlier), and stripping a space in a new entry
in the sysfs debug bdi files to ease parsing.

Please pull!

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

Corrado Zoccolo (3):
      cfq-iosched: fix possible problem with jiffies wraparound
      cfq-iosched: fix think time allowed for seekers
      cfq-iosched: avoid probable slice overrun when idling

Jens Axboe (6):
      cfq-iosched: fix issue with rq-rq merging and fifo list ordering
      block: get rid of kblock_schedule_delayed_work()
      block: use proper BLK_RW_ASYNC in blk_queue_start_tag()
      cfq-iosched: abstract out the 'may this cfqq dispatch' logic
      cfq-iosched: fix the slice residual sign
      cfq-iosched: apply bool value where we return 0/1

KOSAKI Motohiro (1):
      elv_iosched_store(): fix strstrip() misuse

Nikanth Karthikesan (1):
      block: Seperate read and write statistics of in_flight requests v2

Randy Dunlap (1):
      blk-settings: fix function parameter kernel-doc notation

Wu Fengguang (2):
      writeback: account IO throttling wait as iowait
      writeback: kill space in debugfs item name

 block/blk-core.c       |   16 +---
 block/blk-merge.c      |    2 +-
 block/blk-settings.c   |    2 +-
 block/blk-tag.c        |    2 +-
 block/cfq-iosched.c    |  259 ++++++++++++++++++++++++++----------------------
 block/elevator.c       |    4 +-
 block/genhd.c          |    4 +-
 drivers/md/dm.c        |   16 ++-
 fs/partitions/check.c  |   12 ++-
 include/linux/blkdev.h |    4 -
 include/linux/genhd.h  |   21 +++--
 kernel/sched.c         |    3 -
 mm/backing-dev.c       |    2 +-
 mm/page-writeback.c    |    3 +-
 14 files changed, 191 insertions(+), 159 deletions(-)

-- 
Jens Axboe


                 reply	other threads:[~2009-10-12  9:48 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=20091012094803.GB9228@kernel.dk \
    --to=jens.axboe@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox