From: majianpeng <majianpeng@gmail.com>
To: axboe <axboe@kernel.dk>, NeilBrown <neilb@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-raid <linux-raid@vger.kernel.org>
Subject: [PATCH 0/3] handle some bugs for REQ_NOMERGE.
Date: Wed, 30 Oct 2013 10:41:35 +0800 [thread overview]
Message-ID: <2013103010413167237212@gmail.com> (raw)
This patch set mainly handle some bugs for REQ_NOMERGE.
Jianpeng Ma (3):
block: Add REQ_NOMERGE into REQ_COMMON_MASK
block: Check bio can merge before call attempt_plug_merge.
md/raid5: For stripe with R5_ReadNoMerge, we replace REQ_FLUSH with
REQ_NOMERGE.
block/blk-core.c | 2 +-
drivers/md/raid5.c | 2 +-
include/linux/blk_types.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
1.8.4
reply other threads:[~2013-10-30 2:41 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=2013103010413167237212@gmail.com \
--to=majianpeng@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).