linux-kernel - Re: arch/86: AVX RAID5 xor checksumming

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] [day] [month] [year] [list]

Message-ID: <20120414120208.GI24688@gmail.com>
Date:	Sat, 14 Apr 2012 14:02:08 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	NeilBrown <neilb@...e.de>,
	Jim Kukunas <james.t.kukunas@...ux.intel.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org, mingo@...hat.com, tglx@...utronix.de,
	linux-raid@...r.kernel.org
Subject: Re: arch/86: AVX RAID5 xor checksumming


* H. Peter Anvin <hpa@...or.com> wrote:

> On 04/10/2012 01:14 PM, NeilBrown wrote:
> >>
> >> I think this (and the SSSE3 patches for RAID-6) should go in via the
> >> RAID tree.  Neil, do you agree?
> > 
> > I'm happy to take the SSSE3 RAID-6 patches as they only affect lib/raid6, but
> > I felt that this one - being purely in arch/x86 - should probably go via the
> > x86 tree.
> > However I'm flexible and if you (collectively) are happy with these patches
> > going in through my tree, I'll do that.
> > 
> 
> Go ahead and take them with my Acked-by: -- I think that's easier.

Yeah - and x86/include/asm/xor*.h should probably be renamed 
raid_xor*.h or so, to make this really obvious to do in the 
future.

Thanks,

	Ingo
--
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/