From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Arjan van de Ven <arjan@infradead.org>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
venkatesh.pallipadi@intel.com, suresh.b.siddha@intel.com,
Michael Neuling <mikey@neuling.org>,
"Amit K. Arora" <aarora@linux.vnet.ibm.com>
Subject: Re: [RFC PATCH v1 0/3] Scaled statistics using APERF/MPERF in x86
Date: Mon, 02 Jun 2008 11:38:20 +0530 [thread overview]
Message-ID: <48438E54.1000404@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080531211306.GM5405@ucw.cz>
Pavel Machek wrote:
> Hi!
>
>>> entitlement for the process as per the current CPU frequency. This
>>> technique is used in powerpc architecture with the help of hardware
>>> registers that accurately capture the entitlement.
>>>
>> there are some issues with this unfortunately, and these make it
>> a very complex thing to do.
>> Just to mention a few:
>> 1) What if the BIOS no longer allows us to go to the max frequency for
>> a period (for example as a result of overheating); with the approach
>> above, the admin would THINK he can go faster, but he cannot in reality,
>> so there's misleading information (the system looks half busy, while in
>
> Plus time one-second-computation-job returning anything else is just
> wrong. Even when it only happens when overheated... or only on battery
> power.
>
> If you want scaled utime, you need new interface.
We do have a new interface, two new parameters per-task utimescaled and
stimescaled. They already exist in task_struct. Ditto for the delay accounting
pieces. Did I misunderstand your need for a new interface? We still keep utime
and stime around.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
prev parent reply other threads:[~2008-06-02 6:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 14:31 [RFC PATCH v1 0/3] Scaled statistics using APERF/MPERF in x86 Vaidyanathan Srinivasan
2008-05-26 14:31 ` [RFC PATCH v1 1/3] General framework for APERF/MPERF access and accounting Vaidyanathan Srinivasan
2008-05-26 18:11 ` Balbir Singh
2008-05-27 14:54 ` Vaidyanathan Srinivasan
2008-05-26 14:31 ` [RFC PATCH v1 2/3] Make calls to account_scaled_stats Vaidyanathan Srinivasan
2008-05-26 18:18 ` Balbir Singh
2008-05-27 15:02 ` Vaidyanathan Srinivasan
2008-05-29 15:18 ` Michael Neuling
2008-05-29 18:23 ` Vaidyanathan Srinivasan
2008-05-26 14:31 ` [RFC PATCH v1 3/3] Print scaled utime and stime in getdelays Vaidyanathan Srinivasan
2008-05-26 15:50 ` [RFC PATCH v1 0/3] Scaled statistics using APERF/MPERF in x86 Arjan van de Ven
2008-05-26 17:24 ` Balbir Singh
2008-05-26 18:00 ` Arjan van de Ven
2008-05-26 18:36 ` Balbir Singh
2008-05-26 18:51 ` Arjan van de Ven
2008-05-27 12:59 ` Balbir Singh
2008-05-27 13:19 ` Vaidyanathan Srinivasan
2008-05-27 14:15 ` Arjan van de Ven
2008-05-27 15:27 ` Vaidyanathan Srinivasan
2008-05-31 21:27 ` Pavel Machek
2008-06-02 17:54 ` Vaidyanathan Srinivasan
2008-06-03 2:20 ` Arjan van de Ven
2008-05-27 13:29 ` Vaidyanathan Srinivasan
2008-05-27 14:19 ` Arjan van de Ven
2008-05-27 15:20 ` Vaidyanathan Srinivasan
2008-05-27 14:04 ` Vaidyanathan Srinivasan
2008-05-27 16:40 ` Arjan van de Ven
2008-05-27 18:26 ` Vaidyanathan Srinivasan
2008-05-31 21:17 ` Pavel Machek
2008-05-31 21:13 ` Pavel Machek
2008-06-02 6:08 ` Balbir Singh [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=48438E54.1000404@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=aarora@linux.vnet.ibm.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikey@neuling.org \
--cc=pavel@suse.cz \
--cc=suresh.b.siddha@intel.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=venkatesh.pallipadi@intel.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.