From: Neil Brown <neilb@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>,
Matti Aarnio <matti.aarnio@zmailer.org>,
Jesper Juhl <jj@chaosbits.net>,
Prakash Punnoor <prakash@punnoor.de>,
Michael Tokarev <mjt@tls.msk.>
Subject: Re: Proposal: make RAID6 code optional
Date: Sun, 19 Apr 2009 16:28:11 +1000 [thread overview]
Message-ID: <18922.50299.133847.743973@notabene.brown> (raw)
In-Reply-To: message from NeilBrown on Sunday April 19
On Sunday April 19, neilb@suse.de wrote:
>
> In 2.6.30, the Q syndrome code has been moved into a separate module,
> so raid456.ko should be quite a bit smaller.
Of course that doesn't really help as there will be a dependency
between raid456.ko and pq.ko so you cannot avoid having pq.ko loaded
while using raid5.
It might make sense to create a raid6 module that just contains
The call to register_md_personality(raid6_personality) and some
linkage so that the code in raid456.ko can get to the code in pq.ko.
This is probably worth trying one the raid6 async offload stuff
stabilises.
NeilBrown
next prev parent reply other threads:[~2009-04-19 6:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 7:46 Proposal: make RAID6 code optional Prakash Punnoor
2009-04-18 8:09 ` Michael Tokarev
2009-04-18 9:16 ` Prakash Punnoor
2009-04-18 13:56 ` Jesper Juhl
2009-04-18 14:58 ` Matti Aarnio
2009-04-19 2:07 ` H. Peter Anvin
2009-04-19 2:27 ` NeilBrown
2009-04-19 6:28 ` Neil Brown [this message]
2009-04-21 13:58 ` Bill Davidsen
2009-04-21 17:23 ` H. Peter Anvin
2009-04-22 9:01 ` Goswin von Brederlow
2009-04-22 12:34 ` Bill Davidsen
2009-04-22 15:11 ` H. Peter Anvin
2009-04-22 18:00 ` Andre Noll
2009-04-22 18:31 ` Goswin von Brederlow
2009-04-22 18:50 ` Andre Noll
2009-04-22 18:39 ` H. Peter Anvin
2009-04-22 18:57 ` Andre Noll
2009-04-23 1:35 ` H. Peter Anvin
2009-04-23 8:07 ` Andre Noll
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=18922.50299.133847.743973@notabene.brown \
--to=neilb@suse.de \
--cc=hpa@zytor.com \
--cc=jj@chaosbits.net \
--cc=matti.aarnio@zmailer.org \
--cc=mjt@tls.msk. \
--cc=prakash@punnoor.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).