From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Davidsen Subject: Re: Proposal: make RAID6 code optional Date: Wed, 22 Apr 2009 08:34:47 -0400 Message-ID: <49EF0EE7.2090208@tmr.com> References: <200904180946.27722.prakash@punnoor.de> <49E98AD2.8060601@msgid.tls.msk.ru> <200904181117.03418.prakash@punnoor.de> <20090418145850.GD28512@mea-ext.zmailer.org> <49EDD11E.2030309@tmr.com> <49EE00F9.6090000@zytor.com> <87ljptm59f.fsf@frosties.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87ljptm59f.fsf@frosties.localdomain> Sender: linux-raid-owner@vger.kernel.org To: Goswin von Brederlow Cc: "H. Peter Anvin" , Matti Aarnio , Jesper Juhl , Prakash Punnoor , Michael Tokarev , linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org, neilb@suse.de List-Id: linux-raid.ids Goswin von Brederlow wrote: > "H. Peter Anvin" 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 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.