linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: "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.ru>,
	linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	neilb@suse.de
Subject: Re: Proposal: make RAID6 code optional
Date: Wed, 22 Apr 2009 08:34:47 -0400	[thread overview]
Message-ID: <49EF0EE7.2090208@tmr.com> (raw)
In-Reply-To: <87ljptm59f.fsf@frosties.localdomain>

Goswin von Brederlow wrote:
> "H. Peter Anvin" <hpa@zytor.com> writes:
>
>   
>> Bill Davidsen wrote:
>>     
>>> It would seem that that space could be allocated and populated when
>>> raid6 was first used, as part of the initialization. I haven't looked at
>>> that code since it was new, so I might be optimistic about doing it that
>>> way.
>>>       
>> We could use vmalloc() and generate the tables at initialization time.
>> However, having a separate module which exports the raid6 declaration
>> and uses the raid5 module as a subroutine library seems easier.
>>
>> 	-hpa
>>     
>
> Combine the two.
>
> The raid6 module initializes the tables for raid6 and uses the raid5
> module as subroutine library.
>   

My thought was that by saving almost all of the increased size of the 
raid6 capability it greatly reduces the need to have yet another module. 
It doesn't look as if the actual added code for raid6 is all that large.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc

"You are disgraced professional losers. And by the way, give us our money back."
    - Representative Earl Pomeroy,  Democrat of North Dakota
on the A.I.G. executives who were paid bonuses  after a federal bailout.



  reply	other threads:[~2009-04-22 12:34 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
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 [this message]
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=49EF0EE7.2090208@tmr.com \
    --to=davidsen@tmr.com \
    --cc=goswin-v-b@web.de \
    --cc=hpa@zytor.com \
    --cc=jj@chaosbits.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=mjt@tls.msk.ru \
    --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 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).