linux-kernel - Re: [PATCH] Delay accounting, fix incorrect delay time when constantly waiting on runqueue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1213610109.16944.95.camel@twins>
Date:	Mon, 16 Jun 2008 11:55:09 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	bharathravi1@...il.com
Cc:	mingo@...e.hu, linux-kernel@...r.kernel.org,
	dhaval@...ux.vnet.ibm.com, vatsa@...ibm.com, balbir@...ibm.com,
	Madhava K R <madhavakr@...il.com>,
	Ankita Garg <ankita@...ibm.com>
Subject: Re: [PATCH] Delay accounting, fix incorrect delay time when
	constantly waiting on runqueue

On Mon, 2008-06-16 at 15:11 +0530, bharathravi1@...il.com wrote:
> From: Bharath Ravi <bharathravi1@...il.com>
> 
> This patch corrects the incorrect value of per process run-queue wait time
> reported by delay statistics. The anomaly was due to the following reason.
> When a process leaves the CPU and immediately starts waiting for CPU on
> the runqueue (which means it remains in the TASK_RUNNABLE state), the time
> of re-entry into the run-queue is never recorded. Due to this, the waiting time
> on the runqueue from this point of re-entry upto the next time it hits the CPU
> is not accounted for. This is solved by recording the time of re-entry of a
> process leaving the CPU in the sched_info_depart() function IF the process will
> go back to waiting on the run-queue. This IF condition is verified by checking
> whether the process is still in the TASK_RUNNABLE state.
> 
> The patch was tested on 2.6.26-rc6 using two simple CPU hog programs. The
> values noted prior to the fix did not account for the time spent on the
> runqueue waiting. After the fix, the correct values were reported back
> to user space.


Have you considered: http://lkml.org/lkml/2008/6/5/10

I'm sad to say it is still pending in my todo list :-( - sorry Ankita.

> Signed-off-by: Bharath Ravi <bharathravi1@...il.com>
> Signed-off-by: Madhava K R  <madhavakr@...il.com>
> ---
>  kernel/sched_stats.h |    6 ++++++
>  1 files changed, 6 insertions(+), 0 deletions(-)
> 
> diff --git a/kernel/sched_stats.h b/kernel/sched_stats.h
> index a38878e..80179ef 100644
> --- a/kernel/sched_stats.h
> +++ b/kernel/sched_stats.h
> @@ -198,6 +198,9 @@ static inline void sched_info_queued(struct task_struct *t)
>  /*
>   * Called when a process ceases being the active-running process, either
>   * voluntarily or involuntarily.  Now we can calculate how long we ran.
> + * Also, if the process is still in the TASK_RUNNING state, call
> + * sched_info_queued() to mark that it has now again started waiting on
> + * the runqueue.
>   */
>  static inline void sched_info_depart(struct task_struct *t)
>  {
> @@ -206,6 +209,9 @@ static inline void sched_info_depart(struct task_struct *t)
>  
>  	t->sched_info.cpu_time += delta;
>  	rq_sched_info_depart(task_rq(t), delta);
> +
> +	if (t->state == TASK_RUNNING)
> +		sched_info_queued(t);
>  }
>  
>  /*

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/