From: Robert LeBlanc <robert@leblancnet.us>
To: linux-raid@vger.kernel.org
Cc: Robert LeBlanc <robert@leblancnet.us>
Subject: [PATCH v3 0/2] Reorganize raid*_make_request to clean up code
Date: Mon, 5 Dec 2016 13:02:56 -0700 [thread overview]
Message-ID: <20161205200258.6653-1-robert@leblancnet.us> (raw)
In response to Christoph, I've broken the read and writes into their own
functions to make the code even cleaner. Since it is such a big change, I broke
up the commits into this series instead of creating a v2 of the previous patch.
Changes since v2:
Shaohua Li
* Make md_write_start before wait_barrier
* Move I/O in recovery stripe test to write path
* Changed to if/then instead of return in __make_request
Changes since v1:
John Stoffel
* Changed to if/then instead of return in raid1_make_request
Neil Brown
* Moved wait_barrier into raid1_{read,write}_request so that it could be after
->suspend_{hi,lo}. This prevents a write blocking a resync until the suspend
region is moved.
Robert LeBlanc (2):
md/raid1: Refactor raid1_make_request
md/raid10: Refactor raid10_make_request
drivers/md/raid1.c | 259 +++++++++++++++++++++++++++-------------------------
drivers/md/raid10.c | 215 ++++++++++++++++++++++---------------------
2 files changed, 245 insertions(+), 229 deletions(-)
--
2.10.2
next reply other threads:[~2016-12-05 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 20:02 Robert LeBlanc [this message]
2016-12-05 20:02 ` [PATCH v3 1/2] md/raid1: Refactor raid1_make_request Robert LeBlanc
2016-12-05 20:02 ` [PATCH v3 2/2] md/raid10: Refactor raid10_make_request Robert LeBlanc
2016-12-16 19:59 ` Shaohua Li
2016-12-16 20:49 ` Robert LeBlanc
2016-12-05 20:04 ` [PATCH v3 0/2] Reorganize raid*_make_request to clean up code Robert LeBlanc
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=20161205200258.6653-1-robert@leblancnet.us \
--to=robert@leblancnet.us \
--cc=linux-raid@vger.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