linux-kernel - Re: Proposal: make RAID6 code optional

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87vdowlevi.fsf@frosties.localdomain>
Date:	Wed, 22 Apr 2009 20:31:13 +0200
From:	Goswin von Brederlow <goswin-v-b@....de>
To:	Andre Noll <maan@...temlinux.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Bill Davidsen <davidsen@....com>,
	Matti Aarnio <matti.aarnio@...iler.org>,
	Jesper Juhl <jj@...osbits.net>,
	Prakash Punnoor <prakash@...noor.de>,
	Michael Tokarev <mjt@....msk.ru>, linux-kernel@...r.kernel.org,
	linux-raid@...r.kernel.org, neilb@...e.de
Subject: Re: Proposal: make RAID6 code optional

Andre Noll <maan@...temlinux.org> writes:

> On 10:23, H. Peter Anvin wrote:
>
>> 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.
>
> Really? Easier than keeping only two 256-byte arrays for exp() and
> log() and use these at runtime to populate the (dynamically allocated)
> 64K GF multiplication table? That seems to be really simple and would
> still shave off 64K of kernel memory for raid5-only users.
>
> Andre

Oh, you mean when the first raid6 device is started and not when the
module is loaded. That would work.

MfG
        Goswin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/