linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: kernel test robot <xiaolong.ye@intel.com>,
	lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [LKP] [lkp] [f2fs] ec795418c4: fsmark.files_per_sec -36.3% regression
Date: Fri, 12 Aug 2016 09:22:38 +0800	[thread overview]
Message-ID: <20160812012238.GA47037@jaegeuk> (raw)
In-Reply-To: <87vaz6yl8a.fsf@yhuang-mobile.sh.intel.com>

On Thu, Aug 11, 2016 at 03:49:41PM -0700, Huang, Ying wrote:
> Hi, Kim,
> 
> "Huang, Ying" <ying.huang@intel.com> writes:
> >>
> >> [lkp] [f2fs] 3bdad3c7ee: aim7.jobs-per-min -25.3% regression
> >> [lkp] [f2fs] b93f771286: aim7.jobs-per-min -81.2% regression
> >>
> >> In terms of the above regression, I could check that _reproduce_ procedure
> >> includes mounting filesystem only. Is that correct?
> >
> > Sorry, our test system failed to generate reproduce steps for aim7.  We
> > will implement it.
> >
> > - [lkp] [f2fs] 3bdad3c7ee: aim7.jobs-per-min -25.3% regression
> >
> > The disk is one 48G ram disk.  The steps for aim7 is,
> >
> > cat > workfile <<EOF
> > FILESIZE: 1M
> > POOLSIZE: 10M
> > 10 disk_cp
> > EOF
> >
> > (
> > 	echo $HOSTNAME
> > 	echo disk_cp
> >
> > 	echo 1
> > 	echo 3000
> > 	echo 2
> > 	echo 3000
> > 	echo 1
> > ) | ./multitask -t &
> >
> >
> > - [lkp] [f2fs] b93f771286: aim7.jobs-per-min -81.2% regression
> >
> > The disk is 4 12G ram disk, and setup RAID0 on them via mdadm.  The
> > steps for aim7 is,
> >
> > cat > workfile <<EOF
> > FILESIZE: 1M
> > POOLSIZE: 10M
> > 10 sync_disk_rw
> > EOF
> >
> > (
> > 	echo $HOSTNAME
> > 	echo sync_disk_rw
> >
> > 	echo 1
> > 	echo 600
> > 	echo 2
> > 	echo 600
> > 	echo 1
> > ) | ./multitask -t &
> 
> Any update on these 2 regressions?  Is the information is enough for you
> to reproduce?

Sorry, I've had no time to dig this due to business travel now.
I'll check that when back to US.

Thanks,

> 
> Best Regards,
> Huang, Ying

  reply	other threads:[~2016-08-12  1:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18  2:09 [lkp] [f2fs] ec795418c4: fsmark.app_overhead -36.3% regression kernel test robot
2016-07-18 20:27 ` [LKP] " Huang, Ying
2016-08-04 17:00   ` [LKP] [lkp] [f2fs] ec795418c4: fsmark.files_per_sec " Huang, Ying
2016-08-04 17:24     ` Jaegeuk Kim
2016-08-04 17:44       ` Huang, Ying
2016-08-04 18:52         ` Jaegeuk Kim
2016-08-04 20:36           ` Huang, Ying
2016-08-11 22:49             ` Huang, Ying
2016-08-12  1:22               ` Jaegeuk Kim [this message]
2016-08-24 16:51                 ` huang ying
2016-08-27  0:52                   ` Jaegeuk Kim
2016-08-27  2:13                     ` Fengguang Wu
2016-08-30  2:30                       ` Jaegeuk Kim
2016-08-30 16:44                         ` Huang, Ying
2016-09-26  6:26                           ` Huang, Ying
2016-09-26 18:23                             ` Jaegeuk Kim
2016-09-27  0:50                               ` Huang, Ying
2016-09-27  1:41                                 ` Jaegeuk Kim
2016-10-31  3:14                                   ` Huang, Ying
2016-10-31 17:42                                     ` Jaegeuk Kim

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=20160812012238.GA47037@jaegeuk \
    --to=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=xiaolong.ye@intel.com \
    --cc=ying.huang@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).