From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 000 of 4] md: Introduction
Date: Tue, 29 Aug 2006 15:39:11 +1000 [thread overview]
Message-ID: <20060829153414.6475.patches@notabene> (raw)
Following are 4 patches for md, suitable for 2.6.19.
The first three define "congested_fn" functions for various raid level -
I all just found out about the need for these. These could address
responsiveness problems that some people have reported, particularly
while resync is running.
The last improves some messages when resync happens so e.g. it doesn't
like your array is being resynced when you only asked for it to be checked.
Thanks,
NeilBrown
[PATCH 001 of 4] md: Define backing_dev_info.congested_fn for raid0 and linear
[PATCH 002 of 4] md: Define ->congested_fn for raid1, raid10, and multipath
[PATCH 003 of 4] md: Add a ->congested_fn function for raid5/6
[PATCH 004 of 4] md: Make messages about resync/recovery etc more specific.
next reply other threads:[~2006-08-29 5:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 5:39 NeilBrown [this message]
2006-08-29 5:39 ` [PATCH 001 of 4] md: Define backing_dev_info.congested_fn for raid0 and linear NeilBrown
2006-08-29 5:59 ` Andrew Morton
2006-09-04 5:32 ` Neil Brown
2006-08-29 5:39 ` [PATCH 002 of 4] md: Define ->congested_fn for raid1, raid10, and multipath NeilBrown
2006-08-29 6:12 ` Jan Engelhardt
2006-08-29 5:39 ` [PATCH 003 of 4] md: Add a ->congested_fn function for raid5/6 NeilBrown
2006-08-29 5:39 ` [PATCH 004 of 4] md: Make messages about resync/recovery etc more specific NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2006-08-24 7:40 [PATCH 000 of 4] md: Introduction NeilBrown
2006-08-24 22:09 ` Andrew Morton
2006-08-25 8:06 ` Neil Brown
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=20060829153414.6475.patches@notabene \
--to=neilb@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).