All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	Christian Brauner <brauner@kernel.org>,
	WangYuli <wangyuli@uniontech.com>,
	linux-fsdevel@vger.kernel.org, Mateusz Guzik <mjguzik@gmail.com>
Subject: Re: [linux-next:master] [pipe_read]  aaec5a95d5: stress-ng.poll.ops_per_sec 11.1% regression
Date: Mon, 20 Jan 2025 16:50:10 +0100	[thread overview]
Message-ID: <20250120155009.GD7432@redhat.com> (raw)
In-Reply-To: <202501201311.6d25a0b9-lkp@intel.com>

Again, I'll try to take another look tomorrow. Not sure I will find the
explanation though...

But can you help? I know nothing about stress-ng.

Google finds a lot of stress-ng repositories, I've clone the 1st one
https://github.com/ColinIanKing/stress-ng/blob/master/stress-poll.c
hopefully this is what you used.

On 01/20, kernel test robot wrote:
>
>       9.45            -6.3        3.13 ±  9%  perf-profile.calltrace.cycles-pp.pipe_read.vfs_read.ksys_read.do_syscall_64.entry_SYSCALL_64_after_hwframe
> ...
>      10.00            -6.5        3.53 ±  9%  perf-profile.children.cycles-pp.pipe_read
>       2.34            -1.3        1.07 ±  9%  perf-profile.children.cycles-pp.pipe_poll

Could you explain what do these numbers mean and how there are calculated?

"git-grep cycles-pp" find nothing in stress-ng/ and tools/perf/

> kernel test robot noticed a 11.1% regression of stress-ng.poll.ops_per_sec on:

same for ops_per_sec

>       6150           -47.8%       3208        stress-ng.time.percent_of_cpu_this_job_got

same for percent_of_cpu_this_job_got

>       2993           -50.6%       1477        stress-ng.time.system_time
>     711.20           -36.0%     454.85        stress-ng.time.user_time

Is that what I think it is?? Does it run faster?

Or it exits after some timeout and the decrease in system/user_time can be
explained by the change in the mysterious 'percent_of_cpu_this_job_got' above?

Oleg.


  parent reply	other threads:[~2025-01-20 15:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20  6:57 [linux-next:master] [pipe_read] aaec5a95d5: stress-ng.poll.ops_per_sec 11.1% regression kernel test robot
2025-01-20 11:27 ` Mateusz Guzik
2025-01-20 12:22   ` Oleg Nesterov
2025-01-20 12:42     ` Oleg Nesterov
2025-01-20 14:43       ` Oleg Nesterov
2025-01-20 16:56       ` Mateusz Guzik
2025-01-20 20:31         ` Oleg Nesterov
2025-01-20 21:15           ` Mateusz Guzik
2025-01-23 12:56             ` Oleg Nesterov
2025-01-20 15:50 ` Oleg Nesterov [this message]
2025-01-22  8:43   ` Oliver Sang

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=20250120155009.GD7432@redhat.com \
    --to=oleg@redhat.com \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mjguzik@gmail.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=wangyuli@uniontech.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.