From: Michael Tokarev <mjt@tls.msk.ru>
To: Prakash Punnoor <prakash@punnoor.de>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org, neilb@suse.de
Subject: Re: Proposal: make RAID6 code optional
Date: Sat, 18 Apr 2009 12:09:54 +0400 [thread overview]
Message-ID: <49E98AD2.8060601@msgid.tls.msk.ru> (raw)
In-Reply-To: <200904180946.27722.prakash@punnoor.de>
Prakash Punnoor wrote:
> Hi,
>
> as I am using only RAID5 I wonder why the RAID6 code also needs to be built.
> Here is a rough patch of making RAID6 optional (but depending on raid456)
> without reording of functions to minimize ifdef scattering.
> (I also haven't checked yet who needs ASYNC_MEMCPY and ASYNC_XOR...)
> It would probably be nicer to make RAID4/5 and RAID6 independently selectable
> of each other. But that requires more refactoring, as I can see.
Hm. In "old good days" there were 3 independent kernel modules,
named raid4, raid5 and raid6. Later on, they got merged into one
since they share quite alot of the code, and has only a few specific
parts. Now you're trying to separate them back somewhat....
What's your goal? What's the problem you're trying to solve?
/mjt
next prev parent reply other threads:[~2009-04-18 8:09 UTC|newest]
Thread overview: 21+ 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 [this message]
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
2009-04-19 6:28 ` Neil Brown
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=49E98AD2.8060601@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.