Hi Linus,
Here are the core block changes for this merge window. Not a lot of
exciting stuff going on in this round, most of the changes have been on
the driver side of things. That pull request is coming next. This pull
request contains:
- A set of fixes for chained bio handling from Christoph.
- A tag bounds check for blk-mq from Hannes, ensuring that we don't do
something stupid if a device reports an invalid tag value.
- A set of fixes/updates for the CFQ IO scheduler from Jan Kara.
- A set of blk-mq fixes from Keith, adding support for dynamic hardware
queues, and fixing init of max_dev_sectors for stacking devices.
- A fix for the dynamic hw context from Ming.
- Enabling of cgroup writeback support on a block device, from Shaohua.
Please pull!
git://git.kernel.dk/linux-block.git for-4.6/core
----------------------------------------------------------------
Christoph Hellwig (4):
block: don't unecessarily clobber bi_error for chained bios
block: factor out chained bio completion
block: cleanup bio_endio
block: bio_remaining_done() isn't unlikely
Hannes Reinecke (1):
blk-mq: add bounds check on tag-to-rq conversion
Jan Kara (4):
cfq-iosched: Don't group_idle if cfqq has big thinktime
cfq-iosched: Reorder checks in cfq_should_preempt()
cfq-iosched: Allow sync noidle workloads to preempt each other
cfq-iosched: Allow parent cgroup to preempt its child
Keith Busch (3):
blk-mq: dynamic h/w context count
block: Initialize max_dev_sectors to 0
blk-mq: Fix NULL pointer updating nr_requests
Ming Lei (1):
blk-mq: mark request queue as mq asap
Shaohua Li (1):
block-dev: enable writeback cgroup support
block/bio.c | 50 +++++++-------
block/blk-mq-sysfs.c | 9 +--
block/blk-mq.c | 184 ++++++++++++++++++++++++++++++-------------------
block/blk-mq.h | 1 +
block/blk-settings.c | 4 +-
block/cfq-iosched.c | 43 +++++++++---
fs/block_dev.c | 6 +-
include/linux/blk-mq.h | 2 +
8 files changed, 187 insertions(+), 112 deletions(-)
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-block" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
