mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Jens Axboe <axboe@kernel.dk>, Xiao Ni <xni@redhat.com>,
	Song Liu <songliubraving@fb.com>,
	LKML <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@fb.com>,
	lkp@01.org
Subject: Re: [MD] 4bc034d353: aim7.jobs-per-min -86.0% regression
Date: Mon, 08 Apr 2019 17:45:50 +1000	[thread overview]
Message-ID: <875zrpym6p.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20190408071204.GG11264@shao2-debian>

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

On Mon, Apr 08 2019, kernel test robot wrote:

> Greeting,
>
> FYI, we noticed a -86.0% regression of aim7.jobs-per-min due to commit:

That is expected.  The following commit
  2bc13b83e6298486371761de503faeffd15b7534
should restore the performance.

NeilBrown



>
>
> commit: 4bc034d35377196c854236133b07730a777c4aba ("Revert "MD: fix lock contention for flush bios"")
> https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-block.git for-5.2/block
>
> in testcase: aim7
> on test machine: 40 threads Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz with 384G memory
> with following parameters:
>
> 	disk: 4BRD_12G
> 	md: RAID0
> 	fs: xfs
> 	test: sync_disk_rw
> 	load: 300
> 	cpufreq_governor: performance
>
> test-description: AIM7 is a traditional UNIX system level benchmark suite which is used to test and measure the performance of multiuser system.
> test-url: https://sourceforge.net/projects/aimbench/files/aim-suite7/
>
>

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

      reply	other threads:[~2019-04-08  7:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08  7:12 kernel test robot
2019-04-08  7:45 ` NeilBrown [this message]

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=875zrpym6p.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=axboe@fb.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=rong.a.chen@intel.com \
    --cc=songliubraving@fb.com \
    --cc=xni@redhat.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®