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 core bits for 3.4
Date: Fri, 13 Apr 2012 10:00:45 +0200 [thread overview]
Message-ID: <4F87DD2D.4030507@fusionio.com> (raw)
Hi Linus,
It's a nice and quiet round this time, since most of the
tricky stuff has been pushed to 3.5 to give it more time
to mature. After a few hectic block IO core changes for
3.3 and 3.2, I'm quite happy with a slow round.
Really minor stuff in here, the only real functional change is making
the auto-unplug threshold a per-queue entity. The threshold is set so
that it's low enough that we don't hold off IO for too long, but still
big enough to get a nice benefit from the batched insert (and hence
queue lock cost reduction). For raid configurations, this currently
breaks down.
Please pull.
git://git.kernel.dk/linux-block.git for-3.4/core
Andi Kleen (1):
block: use lockdep_assert_held for queue locking
Dan Carpenter (1):
block: blk_alloc_queue_node(): use caller's GFP flags instead of GFP_KERNEL
Shaohua Li (1):
block: make auto block plug flush threshold per-disk based
Tao Ma (2):
block: Make cfq_target_latency tunable through sysfs.
Documentation: Add sysfs ABI change for cfq's target latency.
Documentation/ABI/testing/sysfs-cfq-target-latency | 8 ++++++++
block/blk-core.c | 5 +++--
block/blk-throttle.c | 2 +-
block/cfq-iosched.c | 10 ++++++++--
include/linux/blkdev.h | 18 +++++++-----------
5 files changed, 27 insertions(+), 16 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-cfq-target-latency
--
Jens Axboe
reply other threads:[~2012-04-13 8:13 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=4F87DD2D.4030507@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox