linux-kernel - Re: [PATCH] virtual sched

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: <46A0502E.3060608@goop.org>
Date:	Thu, 19 Jul 2007 23:03:26 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Paul Mackerras <paulus@...ba.org>
CC:	Ingo Molnar <mingo@...e.hu>, Jan Glauber <jang@...ux.vnet.ibm.com>,
	LKML <linux-kernel@...r.kernel.org>, vatsa@...ux.vnet.ibm.com,
	mschwid2@...ux.vnet.ibm.com, efault@....de,
	dmitry.adamushko@...il.com, anton@...ba.org
Subject: Re: [PATCH] virtual sched_clock() for s390

Paul Mackerras wrote:
> Do you think this makes the PURR more useful for CFS, or less?  To me
> it looks like this would mean that CFS can make a more equitable
> distribution of CPU time if, for example, you had 3 runnable tasks on
> a 2-core x dual-threaded machine (4 virtual CPUs).
>   

Sounds reasonable to me.  I've proposed in the past that sched_clock
should be scaled by the cpufreq frequency to achieve the same effect
(ie, measure the actual number of cpu cycles that are really available
to tasks).

But more specifically, what you've described is exactly analogous to
hypervisor stolen time, since one thread steals time from the other.

> BTW, what does "time spent running during sleep" mean?  Does it mean
> "time that other tasks are running while this task is sleeping"?
>   

That's how I interpreted it.  You're only credited for sleeping if
someone else wanted the CPU in the meantime.

    J
-
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/