All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Liu Bo <bo.liu@linux.alibaba.com>,
	lkp@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lkp-robot] [Btrfs]  5239834016:  blogbench.read_score -7.2% regression
Date: Tue, 23 Oct 2018 13:22:53 +0200	[thread overview]
Message-ID: <20181023112253.GP16290@suse.cz> (raw)
In-Reply-To: <20181023065507.GJ24195@shao2-debian>

On Tue, Oct 23, 2018 at 02:55:07PM +0800, kernel test robot wrote:
> Greeting,
> 
> FYI, we noticed a -7.2% regression of blogbench.read_score due to commit:

Thanks.  I've seen some slightly worse performance results in blogbench,
but overall it's better or still acceptable, also confirmed by other
benchmarks. Nothing to worry about.

WARNING: multiple messages have this Message-ID (diff)
From: David Sterba <dsterba@suse.cz>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [Btrfs] 5239834016: blogbench.read_score -7.2% regression
Date: Tue, 23 Oct 2018 13:22:53 +0200	[thread overview]
Message-ID: <20181023112253.GP16290@suse.cz> (raw)
In-Reply-To: <20181023065507.GJ24195@shao2-debian>

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

On Tue, Oct 23, 2018 at 02:55:07PM +0800, kernel test robot wrote:
> Greeting,
> 
> FYI, we noticed a -7.2% regression of blogbench.read_score due to commit:

Thanks.  I've seen some slightly worse performance results in blogbench,
but overall it's better or still acceptable, also confirmed by other
benchmarks. Nothing to worry about.

  reply	other threads:[~2018-10-23 11:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  6:55 [lkp-robot] [Btrfs] 5239834016: blogbench.read_score -7.2% regression kernel test robot
2018-10-23  6:55 ` kernel test robot
2018-10-23 11:22 ` David Sterba [this message]
2018-10-23 11:22   ` David Sterba

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=20181023112253.GP16290@suse.cz \
    --to=dsterba@suse.cz \
    --cc=bo.liu@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=rong.a.chen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.