public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: "Chen, Rong A" <rong.a.chen@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Hugh Dickins <hughd@google.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Matthew Auld <matthew.auld@intel.com>,
	William Kucharski <william.kucharski@oracle.com>,
	Qian Cai <cai@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org, lkp@intel.com, zhengjun.xing@intel.com
Subject: Re: [LKP] Re: [mm] e6e88712e4: stress-ng.tmpfs.ops_per_sec -69.7% regression
Date: Sat, 31 Oct 2020 14:10:49 +0800	[thread overview]
Message-ID: <20201031061049.GA25495@intel.com> (raw)
In-Reply-To: <20201030145835.GL27442@casper.infradead.org>

On Fri, Oct 30, 2020 at 02:58:35PM +0000, Matthew Wilcox wrote:
> On Fri, Oct 30, 2020 at 10:02:45PM +0800, Chen, Rong A wrote:
> > On 10/30/2020 9:17 PM, Matthew Wilcox wrote:
> > > On Fri, Oct 30, 2020 at 03:17:15PM +0800, kernel test robot wrote:
> > > > Details are as below:
> > > > -------------------------------------------------------------------------------------------------->
> > > > 
> > > > 
> > > > To reproduce:
> > > > 
> > > >          git clone https://github.com/intel/lkp-tests.git
> > > >          cd lkp-tests
> > > >          bin/lkp install job.yaml  # job file is attached in this email
> > > >          bin/lkp run     job.yaml
> > > 
> > > Do you actually test these instructions before you send them out?
> > > 
> > > hdd_partitions: "/dev/disk/by-id/ata-WDC_WD2500BEKT-00PVMT0_WD-WX11A23L4840-part
> > > 1"
> > > ssd_partitions: "/dev/nvme1n1p1 /dev/nvme0n1p1"
> > > rootfs_partition: "/dev/disk/by-id/ata-INTEL_SSDSC2CW240A3_CVCV204303WP240CGN-part1"
> > > 
> > > That's _very_ specific to a given machine.  I'm not familiar with
> > > this test, so I don't know what I need to change.
> > 
> > 
> > Hi Matthew,
> > 
> > Sorry about that, I copied the job.yaml file from the server,
> > the right way to do is to set your disk partitions in the yaml,
> > please see https://github.com/intel/lkp-tests#run-your-own-disk-partitions.
> > 
> > there is another reproduce script attached in the original mail
> > for your reference.
> 
> Can you reproduce this?  Here's my results:
thanks for quick check, we will provide update right after the weekend. Sorry
for any inconvenience for the reproduction side so far. We need to improve
this part.

> 
> # stress-ng "--timeout" "100" "--times" "--verify" "--metrics-brief" "--sequential" "96" "--class" "memory" "--minimize" "--exclude" "spawn,exec,swap,stack,atomic,bad-altstack,bsearch,context,full,heapsort,hsearch,judy,lockbus,lsearch,malloc,matrix-3d,matrix,mcontend,membarrier,memcpy,memfd,memrate,memthrash,mergesort,mincore,null,numa,pipe,pipeherd,qsort,radixsort,remap,resources,rmap,shellsort,skiplist,stackmmap,str,stream,tlb-shootdown,tree,tsearch,vm-addr,vm-rw,vm-segv,vm,wcs,zero,zlib"
> stress-ng: info:  [7670] disabled 'oom-pipe' as it may hang or reboot the machine (enable it with the --pathological option)
> stress-ng: info:  [7670] dispatching hogs: 96 tmpfs
> stress-ng: info:  [7670] successful run completed in 100.23s (1 min, 40.23 secs)
> stress-ng: info:  [7670] stressor       bogo ops real time  usr time  sys time   bogo ops/s   bogo ops/s
> stress-ng: info:  [7670]                           (secs)    (secs)    (secs)   (real time) (usr+sys time)
> stress-ng: info:  [7670] tmpfs              8216    100.10    368.02    230.89        82.08        13.72
> stress-ng: info:  [7670] for a 100.23s run time:
> stress-ng: info:  [7670]     601.38s available CPU time
> stress-ng: info:  [7670]     368.71s user time   ( 61.31%)
> stress-ng: info:  [7670]     231.55s system time ( 38.50%)
> stress-ng: info:  [7670]     600.26s total time  ( 99.81%)
> stress-ng: info:  [7670] load average: 78.32 27.87 10.10
> _______________________________________________
> LKP mailing list -- lkp@lists.01.org
> To unsubscribe send an email to lkp-leave@lists.01.org

  reply	other threads:[~2020-10-31  6:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30  7:17 [mm] e6e88712e4: stress-ng.tmpfs.ops_per_sec -69.7% regression kernel test robot
2020-10-30 13:17 ` Matthew Wilcox
2020-10-30 14:02   ` Chen, Rong A
2020-10-30 14:58     ` Matthew Wilcox
2020-10-31  6:10       ` Philip Li [this message]
2020-11-02  5:21       ` Rong Chen
2020-11-02 14:23         ` Matthew Wilcox
2020-11-06 20:55         ` Matthew Wilcox
2020-11-09  8:10           ` [LKP] " Xing Zhengjun

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=20201031061049.GA25495@intel.com \
    --to=philip.li@intel.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cai@redhat.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=matthew.auld@intel.com \
    --cc=rong.a.chen@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=william.kucharski@oracle.com \
    --cc=willy@infradead.org \
    --cc=zhengjun.xing@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