linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sieber, Fernand" <sieberf@amazon.com>
To: "20240613185906.31082-1-sieberf@amazon.com"
	<20240613185906.31082-1-sieberf@amazon.com>
Cc: "linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	"Arnaldo Carvalho de Melo" <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH] perf: Timehist account sch delay for scheduled out running
Date: Tue, 18 Jun 2024 08:44:34 +0000	[thread overview]
Message-ID: <e78393a53b49416088b4d3e849f75686@amazon.com> (raw)
In-Reply-To: <1bb99f6f-532f-47cb-963c-c5c0262e383c@linux.ibm.com>

Hi Maladi,

Ok, thanks for the feedback. I will submit another revision with the updated man page then. In my opinion it makes more sense to measure the scheduling delay as the runnable delay (wakeup and pre empted), as we need to consider both cases when benchmarking scheduling policies. However if there is/was a specific reason to restrict scheduling delay in timehist as the measure of wakeup delay only please let me know.

--Fernand

      reply	other threads:[~2024-06-18  8:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 18:59 [PATCH] perf: Timehist account sch delay for scheduled out running Fernand Sieber
2024-06-15 20:50 ` Madadi Vineeth Reddy
2024-06-18  8:44   ` Sieber, Fernand [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=e78393a53b49416088b4d3e849f75686@amazon.com \
    --to=sieberf@amazon.com \
    --cc=20240613185906.31082-1-sieberf@amazon.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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 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).