From: NeilBrown <neilb@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-raid@vger.kernel.org, Shaohua Li <shli@kernel.org>
Subject: [PATCH 0/4] Plugging changes for blk/md/umem
Date: Thu, 26 Jul 2012 12:58:29 +1000 [thread overview]
Message-ID: <20120726025650.32180.65163.stgit@notabene.brown> (raw)
Hi Jens,
the following series makes a number of changes to plugging, moving
common code from md and umem into block, and modifying it to allow
md to get more value out of it.
They've been sitting in -next for a while.
Are you OK with me forwarding them to Linus, or would you rather they
went though your tree?
Thanks,
NeilBrown
---
NeilBrown (3):
blk: pass from_schedule to non-request unplug functions.
blk: centralize non-request unplug handling.
md: remove plug_cnt feature of plugging.
Shaohua Li (1):
block: stack unplug
block/blk-core.c | 44 ++++++++++++++++++++++++++++--------
drivers/block/umem.c | 37 ++++++------------------------
drivers/md/md.c | 59 ++++--------------------------------------------
drivers/md/md.h | 11 ++++++---
drivers/md/raid1.c | 3 +-
drivers/md/raid10.c | 3 +-
drivers/md/raid5.c | 5 ++--
include/linux/blkdev.h | 8 +++++--
8 files changed, 63 insertions(+), 107 deletions(-)
--
Signature
next reply other threads:[~2012-07-26 2:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 2:58 NeilBrown [this message]
2012-07-26 2:58 ` [PATCH 1/4] md: remove plug_cnt feature of plugging NeilBrown
2012-07-26 2:58 ` [PATCH 3/4] block: stack unplug NeilBrown
2012-07-26 2:58 ` [PATCH 4/4] blk: pass from_schedule to non-request unplug functions NeilBrown
2012-07-26 2:58 ` [PATCH 2/4] blk: centralize non-request unplug handling NeilBrown
2012-07-31 7:08 ` [PATCH 0/4] Plugging changes for blk/md/umem Jens Axboe
2012-07-31 7:25 ` NeilBrown
2012-07-31 7:33 ` Jens Axboe
2012-07-31 8:44 ` NeilBrown
2012-07-31 8:54 ` 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=20120726025650.32180.65163.stgit@notabene.brown \
--to=neilb@suse.de \
--cc=axboe@kernel.dk \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.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;
as well as URLs for NNTP newsgroup(s).