Hi Steve,
On Wed, Mar 30, 2016 at 06:35:23PM -0700, Steve Muckle wrote:
> This series was dropped in favor of Rafael's schedutil. But on the
> chance that you're still curious about the test setup used to quantify
> the series I'll explain below.
I will catch up and learn both.
> These results
Hi Steve,
On Wed, Mar 30, 2016 at 06:35:23PM -0700, Steve Muckle wrote:
> This series was dropped in favor of Rafael's schedutil. But on the
> chance that you're still curious about the test setup used to quantify
> the series I'll explain below.
I will catch up and learn both.
> These results
Hi Yuyang,
This series was dropped in favor of Rafael's schedutil. But on the
chance that you're still curious about the test setup used to quantify
the series I'll explain below.
On 03/29/2016 05:45 PM, Yuyang Du wrote:
> Hi Steve,
>
> On Mon, Feb 22, 2016 at 05:22:40PM -0800, Steve Muckle
Hi Yuyang,
This series was dropped in favor of Rafael's schedutil. But on the
chance that you're still curious about the test setup used to quantify
the series I'll explain below.
On 03/29/2016 05:45 PM, Yuyang Du wrote:
> Hi Steve,
>
> On Mon, Feb 22, 2016 at 05:22:40PM -0800, Steve Muckle
Hi Steve,
On Mon, Feb 22, 2016 at 05:22:40PM -0800, Steve Muckle wrote:
> The number of times the busy
> duration exceeds the period of the periodic workload (an "overrun") is
> also recorded.
Could you please explain more about overrun?
> SCHED_OTHER workload:
> wload parameters
Hi Steve,
On Mon, Feb 22, 2016 at 05:22:40PM -0800, Steve Muckle wrote:
> The number of times the busy
> duration exceeds the period of the periodic workload (an "overrun") is
> also recorded.
Could you please explain more about overrun?
> SCHED_OTHER workload:
> wload parameters
On 02/22/2016 05:22 PM, Steve Muckle wrote:
> Scheduler-driven CPU frequency selection hopes to exploit both
> per-task and global information in the scheduler to improve frequency
> selection policy and achieve lower power consumption, improved
> responsiveness/performance, and less reliance on
On 02/22/2016 05:22 PM, Steve Muckle wrote:
> Scheduler-driven CPU frequency selection hopes to exploit both
> per-task and global information in the scheduler to improve frequency
> selection policy and achieve lower power consumption, improved
> responsiveness/performance, and less reliance on
Scheduler-driven CPU frequency selection hopes to exploit both
per-task and global information in the scheduler to improve frequency
selection policy and achieve lower power consumption, improved
responsiveness/performance, and less reliance on heuristics and
tunables. For further discussion of
Scheduler-driven CPU frequency selection hopes to exploit both
per-task and global information in the scheduler to improve frequency
selection policy and achieve lower power consumption, improved
responsiveness/performance, and less reliance on heuristics and
tunables. For further discussion of
10 matches
Mail list logo
