From: NeilBrown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Subject: [PATCH] md - 0 of 7 - Introduction
Date: Fri, 06 Feb 2004 16:35:51 +1100 [thread overview]
Message-ID: <20040206162532.30220.patches@notabene> (raw)
Hi again.
Here are 7 patches for md in 2.4.3-pre-current
The first flags the START_ARRAY as deprecated - I plan to remove it in 2.7.
The comment with that patch explains why.
The next 5 provide some cleanup of raid1 code leading to a patch which
enabled raid1 to safely use large requests when resyncing (it uses
bio_add_page to make sure each page is allowed). This substantially increases
resync speed in atleast one test.
The final patch in a new version of the partitioning patch.
It removes the rather ugly code for forcing the partitions to be
re-evaluated and instead makes simple arranges for them to be reread
on the next open. This fixes the one bug that was reported against the
patch.
I have also taken onboard some of the feedback I got about the patch.
NeilBrown
next reply other threads:[~2004-02-06 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 5:35 NeilBrown [this message]
2004-02-06 5:35 ` [PATCH] md - 1 of 7 - Print "deprecated" warning when START_ARRAY is used NeilBrown
2004-02-06 5:35 ` [PATCH] md - 2 of 7 - Split read and write end_request handlers NeilBrown
2004-02-06 5:35 ` [PATCH] md - 3 of 7 - Discard the cmd field from r1_bio structure NeilBrown
2004-02-06 5:35 ` [PATCH] md - 4 of 7 - Remove some un-needed fields from r1bio_s NeilBrown
2004-02-06 5:35 ` [PATCH] md - 5 of 7 - Avoid unnecessary bio allocation during raid1 resync NeilBrown
2004-02-06 5:35 ` [PATCH] md - 6 of 7 - Dynamically limit size of bio requests used for " NeilBrown
2004-02-06 5:35 ` [PATCH] md - 7 of 7 - Allow partitioning of MD devices NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2004-01-23 0:13 [PATCH] md - 0 of 7 - Introduction NeilBrown
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=20040206162532.30220.patches@notabene \
--to=neilb@cse.unsw.edu.au \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-raid@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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).