From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] core block IO bits for 3.8
Date: Mon, 17 Dec 2012 16:34:26 +0100 [thread overview]
Message-ID: <50CF3B82.9000904@kernel.dk> (raw)
Hi Linus,
Here are the core block IO bits for 3.8. The branch contains:
- The final version of the surprise device removal fixups from Bart.
- Don't hide EFI partitions under advanced partition types. It's fairly
wide spread these days. This is especially dangerous for systems that
have both msdos and efi partition tables, where you want to keep them
in sync.
- Cleanup of using -1 instead of the proper NUMA_NO_NODE
- Export control of bdi flusher thread CPU mask and default to using the
home node (if known) from Jeff.
- Export unplug tracepoint for MD.
- Core improvements from Shaohua. Reinstate the recursive merge, as the
original bug has been fixed. Add plugging for discard and also fix a
problem handling non pow-of-2 discard limits.
Please pull! There's a trivial merge in block/blk-exec.c due to a fix
that went into 3.7-rc at a later point than -rc4 where this is based.
git://git.kernel.dk/linux-block.git for-3.8/core
----------------------------------------------------------------
Bart Van Assche (6):
block: Rename queue dead flag
block: Let blk_drain_queue() caller obtain the queue lock
block: Avoid that request_fn is invoked on a dead queue
block: Avoid scheduling delayed work on a dead queue
block: Make blk_cleanup_queue() wait until request_fn finished
bsg: Remove unused function bsg_goose_queue()
Diego Calleja (1):
partitions: enable EFI/GPT support by default
Ezequiel Garcia (1):
block: use NUMA_NO_NODE instead of -1
Jeff Moyer (1):
bdi: add a user-tunable cpu_list for the bdi flusher threads
NeilBrown (1):
block: export block_unplug tracepoint
Shaohua Li (4):
block CFQ: avoid moving request to different queue
block: recursive merge requests
block: discard granularity might not be power of 2
block: add plug for blkdev_issue_discard
xiaobing tu (1):
deadline: Allow 0ms deadline latency, increase the read speed
block/blk-cgroup.c | 2 +-
block/blk-core.c | 127 ++++++++++++++++++++++++++-----------------
block/blk-exec.c | 4 +-
block/blk-lib.c | 26 +++++----
block/blk-settings.c | 6 +-
block/blk-sysfs.c | 4 +-
block/blk-throttle.c | 2 +-
block/blk.h | 4 +-
block/bsg-lib.c | 13 -----
block/cfq-iosched.c | 3 +-
block/deadline-iosched.c | 2 +-
block/elevator.c | 16 ++++--
block/genhd.c | 2 +-
block/partitions/Kconfig | 4 +-
drivers/scsi/scsi_lib.c | 2 +-
include/linux/backing-dev.h | 4 ++
include/linux/blkdev.h | 17 ++++--
include/linux/bsg-lib.h | 1 -
mm/backing-dev.c | 84 ++++++++++++++++++++++++++++
19 files changed, 224 insertions(+), 99 deletions(-)
--
Jens Axboe
next reply other threads:[~2012-12-17 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 15:34 Jens Axboe [this message]
2012-12-17 16:06 ` [GIT PULL] core block IO bits for 3.8 Jeff Moyer
2012-12-17 17:00 ` Tejun Heo
2012-12-17 17:04 ` Jens Axboe
2012-12-17 17:08 ` Linus Torvalds
2012-12-17 17:09 ` Jens Axboe
2012-12-17 17:15 ` Jeff Moyer
2012-12-17 19:06 ` Jens Axboe
2012-12-17 19:27 ` Linus Torvalds
2012-12-17 19:28 ` Jens Axboe
2012-12-17 19:38 ` Shentino
2012-12-17 17:47 ` Tejun Heo
2012-12-17 19:07 ` 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=50CF3B82.9000904@kernel.dk \
--to=axboe@kernel.dk \
--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