linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "kernel test robot" <xiaolong.ye@intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Andy Lutomirski" <luto@amacapital.net>,
	"Brian Gerst" <brgerst@gmail.com>,
	"Denys Vlasenko" <dvlasenk@redhat.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org
Subject: Re: [lkp] [x86/hweight]  65ea11ec6a:  will-it-scale.per_process_ops 9.3% improvement
Date: Tue, 16 Aug 2016 19:16:35 +0200	[thread overview]
Message-ID: <20160816171635.GA10542@nazgul.tnic> (raw)
In-Reply-To: <9FF32F53-5EF8-40D4-B696-A30FDF7201E1@zytor.com>

On Tue, Aug 16, 2016 at 09:59:00AM -0700, H. Peter Anvin wrote:
> Dang...

Isn't 9.3% improvement a good thing(tm) ?

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--

  reply	other threads:[~2016-08-16 17:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 14:26 [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement kernel test robot
2016-08-16 16:59 ` H. Peter Anvin
2016-08-16 17:16   ` Borislav Petkov [this message]
2016-08-16 23:09     ` H. Peter Anvin
2016-08-17  5:46       ` Borislav Petkov
2016-08-17 22:29         ` [LKP] " Huang, Ying
2016-08-18  3:45           ` Borislav Petkov
2016-08-18  3:54             ` Huang, Ying
2016-08-18  4:11               ` Borislav Petkov
2016-08-25  9:22                 ` Borislav Petkov
2016-08-25 10:05                   ` H. Peter Anvin
2016-08-25 11:45                     ` Borislav Petkov
2016-08-25 20:07                       ` H. Peter Anvin
2016-08-18  3:57             ` H. Peter Anvin
2016-08-17  6:48       ` Peter Zijlstra

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=20160816171635.GA10542@nazgul.tnic \
    --to=bp@suse.de \
    --cc=brgerst@gmail.com \
    --cc=dvlasenk@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=luto@amacapital.net \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=ville.syrjala@linux.intel.com \
    --cc=xiaolong.ye@intel.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).