public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3, v2] x86: xor-block handling adjustments
Date: Fri, 25 Jan 2013 09:25:30 +0100	[thread overview]
Message-ID: <20130125082530.GE25314@gmail.com> (raw)
In-Reply-To: <51024E9602000078000B97A2@nat28.tlf.novell.com>


* Jan Beulich <JBeulich@suse.com> wrote:

> >>> On 24.01.13 at 18:32, "H. Peter Anvin" <hpa@zytor.com> wrote:
> > On 01/24/2013 11:15 AM, Ingo Molnar wrote:
> >> 
> >> * Jan Beulich <JBeulich@suse.com> wrote:
> >> 
> >>> v2 of this series is merely updated on top of the changes between
> >>> 3.6 and 3.7-rc (which includes the dropping of what previously was
> >>> the second patch in a four patch series).
> >>>
> >>> 1: unify SSE-base xor-block routines
> >>> 2: add alternative SSE implementation only prefetching once per 64-byte line
> >>> 3: make virtualization friendly
> >>>
> >>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> >> 
> >> Looks useful. Wondering what the status is: hpa, was your 
> >> concern resolved, do you think we can apply these?
> >> 
> > 
> > I don't see anything wrong, except that I can't *find* patch 
> > 3/3 either in my inbox nor on LKML...

I think it's just that this is an older thread I found, possibly 
out of your folder already.

They are looking good to me and I've applied them to x86/asm to 
give it some testing as well. Please holler if you see something 
funny.

Thanks,

	Ingo

  reply	other threads:[~2013-01-25  8:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02 14:17 [PATCH 0/3, v2] x86: xor-block handling adjustments Jan Beulich
2013-01-24 17:15 ` Ingo Molnar
2013-01-24 17:32   ` H. Peter Anvin
2013-01-25  8:21     ` Jan Beulich
2013-01-25  8:25       ` Ingo Molnar [this message]
2013-01-25 19:29       ` H. Peter Anvin
2013-01-26 12:08         ` Ingo Molnar
2013-01-26 15:13           ` 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=20130125082530.GE25314@gmail.com \
    --to=mingo@kernel.org \
    --cc=JBeulich@suse.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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