From: Rick Lindsley <ricklind@linux.vnet.ibm.com>
To: lkp@lists.01.org
Subject: Re: [kernfs] ea7c5fc39a: stress-ng.stream.ops_per_sec 11827.2% improvement
Date: Wed, 10 Jun 2020 19:20:20 -0700 [thread overview]
Message-ID: <197fbd55-f702-e84f-2981-e8a3a32e178a@linux.vnet.ibm.com> (raw)
In-Reply-To: <20200611020657.GI12456@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
On 6/10/20 7:06 PM, kernel test robot wrote:
> On Sun, Jun 07, 2020 at 09:13:08AM +0800, Ian Kent wrote:
>
> It seems the result of stress-ng is inaccurate if test time too
> short, we'll increase the test time to avoid unreasonable results,
> sorry for the inconvenience.
Thank you for your response! I was examining the 25 tests in the 'cpu-cache' class and had nothing but head scratching so far on what could be having that effect.
Rick
WARNING: multiple messages have this Message-ID (diff)
From: Rick Lindsley <ricklind@linux.vnet.ibm.com>
To: kernel test robot <rong.a.chen@intel.com>, Ian Kent <raven@themaw.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>, Tejun Heo <tj@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
David Howells <dhowells@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
lkp@lists.01.org
Subject: Re: [kernfs] ea7c5fc39a: stress-ng.stream.ops_per_sec 11827.2% improvement
Date: Wed, 10 Jun 2020 19:20:20 -0700 [thread overview]
Message-ID: <197fbd55-f702-e84f-2981-e8a3a32e178a@linux.vnet.ibm.com> (raw)
In-Reply-To: <20200611020657.GI12456@shao2-debian>
On 6/10/20 7:06 PM, kernel test robot wrote:
> On Sun, Jun 07, 2020 at 09:13:08AM +0800, Ian Kent wrote:
>
> It seems the result of stress-ng is inaccurate if test time too
> short, we'll increase the test time to avoid unreasonable results,
> sorry for the inconvenience.
Thank you for your response! I was examining the 25 tests in the 'cpu-cache' class and had nothing but head scratching so far on what could be having that effect.
Rick
next prev parent reply other threads:[~2020-06-11 2:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 5:46 [PATCH 0/4] kernfs: proposed locking and concurrency improvement Ian Kent
2020-05-25 5:47 ` [PATCH 1/4] kernfs: switch kernfs to use an rwsem Ian Kent
2020-06-06 15:52 ` [kernfs] ea7c5fc39a: stress-ng.stream.ops_per_sec 11827.2% improvement kernel test robot
2020-06-06 15:52 ` kernel test robot
2020-06-06 18:18 ` Greg Kroah-Hartman
2020-06-06 18:18 ` Greg Kroah-Hartman
2020-06-07 1:13 ` Ian Kent
2020-06-11 2:06 ` kernel test robot
2020-06-11 2:06 ` kernel test robot
2020-06-11 2:20 ` Rick Lindsley [this message]
2020-06-11 2:20 ` Rick Lindsley
2020-06-11 3:02 ` Ian Kent
2020-06-11 3:02 ` Ian Kent
2020-06-07 8:40 ` [PATCH 1/4] kernfs: switch kernfs to use an rwsem Ian Kent
2020-06-08 9:58 ` Ian Kent
2020-05-25 5:47 ` [PATCH 2/4] kernfs: move revalidate to be near lookup Ian Kent
2020-05-25 5:47 ` [PATCH 3/4] kernfs: improve kernfs path resolution Ian Kent
2020-05-25 5:47 ` [PATCH 4/4] kernfs: use revision to identify directory node changes Ian Kent
2020-05-25 6:16 ` [PATCH 0/4] kernfs: proposed locking and concurrency improvement Greg Kroah-Hartman
2020-05-25 7:23 ` Ian Kent
2020-05-25 7:31 ` Greg Kroah-Hartman
2020-05-27 12:44 ` Rick Lindsley
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=197fbd55-f702-e84f-2981-e8a3a32e178a@linux.vnet.ibm.com \
--to=ricklind@linux.vnet.ibm.com \
--cc=lkp@lists.01.org \
/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.