linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Jim Kukunas <james.t.kukunas@linux.intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Paul Menzel <pm.debian@googlemail.com>,
	Linux Raid <linux-raid@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] lib/raid6: Add AVX2 optimized recovery functions
Date: Mon, 19 Nov 2012 11:57:28 +1100	[thread overview]
Message-ID: <20121119115728.2d175646@notabene.brown> (raw)
In-Reply-To: <20121109195610.GA2928@jtkukuna_gentoo_sb.jf.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]

On Fri, 9 Nov 2012 11:56:10 -0800 Jim Kukunas
<james.t.kukunas@linux.intel.com> wrote:

> On Fri, Nov 09, 2012 at 10:50:25PM +1100, Neil Brown wrote:
> > On Fri, 09 Nov 2012 12:39:05 +0100 "H. Peter Anvin" <hpa@zytor.com> wrote:
> > 
> > > Sorry, we cannot share those at this time since the hardwarenis not yet released.
> > 
> > Can I take that to imply "Acked-by: "H. Peter Anvin" <hpa@zytor.com>" ??
> > 
> > It would be nice to have at least a statement like:
> >  These patches have been tested both with the user-space testing tool and in 
> >  a RAID6 md array and the pass all test.  While we cannot release performance
> >  numbers as the hardwere is not released, we can confirm that on that hardware
> >  the performance with these patches is faster than without.
> > 
> > I guess I should be able to assume that - surely the patches would not be
> > posted if it were not true...  But I like to avoid assuming when I can.
> 
> Hi Neil,
> 
> That assumption is correct. The patch was tested and benchmarked before submission.

Thanks.  I've queued the patch up.
> 
> You'll notice that this code is very similar to the SSSE3-optimized
> recovery routines I wrote earlier. This implementation extends that same
> algorithm from 128-bit registers to 256-bit registers.

I might notice that if I actually looked, but it all starts swimming before
my eyes when I try :-)
If both you and hpa like it, then that is good enough for me.

Thanks,
NeilBrown


> 
> Thanks.
> 


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-11-19  0:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08 21:47 [PATCH] lib/raid6: Add AVX2 optimized recovery functions Jim Kukunas
2012-11-09 11:35 ` Paul Menzel
2012-11-09 11:39   ` H. Peter Anvin
2012-11-09 11:46     ` Paul Menzel
2012-11-09 11:50     ` NeilBrown
2012-11-09 12:24       ` H. Peter Anvin
2012-11-09 19:56       ` Jim Kukunas
2012-11-19  0:57         ` NeilBrown [this message]
2012-11-29 20:09 ` Andi Kleen
2012-11-29 21:13   ` H. Peter Anvin
2012-11-29 21:18     ` Andi Kleen
2012-11-29 22:27       ` H. Peter Anvin
2012-11-29 22:28       ` H. Peter Anvin

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=20121119115728.2d175646@notabene.brown \
    --to=neilb@suse.de \
    --cc=hpa@zytor.com \
    --cc=james.t.kukunas@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=pm.debian@googlemail.com \
    /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).