mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: NeilBrown <neilb@suse.de>
Cc: Paul Menzel <pm.debian@googlemail.com>,
	Jim Kukunas <james.t.kukunas@linux.intel.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: Fri, 09 Nov 2012 13:24:56 +0100	[thread overview]
Message-ID: <71d4fc0f-f147-4cc6-8626-d1f255a2f7f7@email.android.com> (raw)
In-Reply-To: <20121109225025.13a846ca@notabene.brown>

Yes, consider it an implicit Acked-by.

NeilBrown <neilb@suse.de> 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.
>
>Thanks,
>NeilBrown
>
>
>> 
>> Paul Menzel <pm.debian@googlemail.com> wrote:
>> 
>> >Dear Jim,
>> >
>> >
>> >Am Donnerstag, den 08.11.2012, 13:47 -0800 schrieb Jim Kukunas:
>> >> Optimize RAID6 recovery functions to take advantage of
>> >> the 256-bit YMM integer instructions introduced in AVX2.
>> >
>> >in my experiencing optimizations always have to be back up by
>> >benchmarks. Could you add those to the commit message please.
>> >
>> >> Signed-off-by: Jim Kukunas <james.t.kukunas@linux.intel.com>
>> >
>> >[…]
>> >
>> >
>> >Thanks,
>> >
>> >Paul
>> 

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.

  reply	other threads:[~2012-11-09 12:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08 21:47 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 [this message]
2012-11-09 19:56       ` Jim Kukunas
2012-11-19  0:57         ` NeilBrown
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=71d4fc0f-f147-4cc6-8626-d1f255a2f7f7@email.android.com \
    --to=hpa@zytor.com \
    --cc=james.t.kukunas@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --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

all inboxes | Powered by JetHome®