On Wed, May 16, 2018 at 10:55:13AM -0700, Srinivas Pandruvada wrote:
> On Wed, 2018-05-16 at 09:37 +0200, Peter Zijlstra wrote:
> > On Tue, May 15, 2018 at 09:49:06PM -0700, Srinivas Pandruvada wrote:
> > Hurmph, this looks like you're starting to duplicate the schedutil
> > iowait logic. Why
On Wed, May 16, 2018 at 10:55:13AM -0700, Srinivas Pandruvada wrote:
> On Wed, 2018-05-16 at 09:37 +0200, Peter Zijlstra wrote:
> > On Tue, May 15, 2018 at 09:49:06PM -0700, Srinivas Pandruvada wrote:
> > Hurmph, this looks like you're starting to duplicate the schedutil
> > iowait logic. Why
On Wed, 2018-05-16 at 11:45 +0200, Rafael J. Wysocki wrote:
[...]
>
> > + if (time_before64(time, cpu->last_io_update + 2 *
> > TICK_NSEC) &&
> > + intel_pstate_check_boost_threhold(cpu))
> > + cpu->iowait_boost = true;
> > +
> > +
On Wed, 2018-05-16 at 11:45 +0200, Rafael J. Wysocki wrote:
[...]
>
> > + if (time_before64(time, cpu->last_io_update + 2 *
> > TICK_NSEC) &&
> > + intel_pstate_check_boost_threhold(cpu))
> > + cpu->iowait_boost = true;
> > +
> > +
On Wed, 2018-05-16 at 09:37 +0200, Peter Zijlstra wrote:
> On Tue, May 15, 2018 at 09:49:06PM -0700, Srinivas Pandruvada wrote:
[...]
> >
@@ -258,6 +261,8 @@ struct cpudata {
> > s16 epp_saved;
> > u64 hwp_req_cached;
> > call_single_data_t csd;
> > + bool hwp_boost_active;
> > +
On Wed, 2018-05-16 at 09:37 +0200, Peter Zijlstra wrote:
> On Tue, May 15, 2018 at 09:49:06PM -0700, Srinivas Pandruvada wrote:
[...]
> >
@@ -258,6 +261,8 @@ struct cpudata {
> > s16 epp_saved;
> > u64 hwp_req_cached;
> > call_single_data_t csd;
> > + bool hwp_boost_active;
> > +
On Wed, May 16, 2018 at 6:49 AM, Srinivas Pandruvada
wrote:
> When a task is woken up from IO wait, boost HWP prformance to max. This
> helps IO workloads on servers with per core P-states. But changing limits
> has extra over head of issuing new HWP Request
On Wed, May 16, 2018 at 6:49 AM, Srinivas Pandruvada
wrote:
> When a task is woken up from IO wait, boost HWP prformance to max. This
> helps IO workloads on servers with per core P-states. But changing limits
> has extra over head of issuing new HWP Request MSR, which takes 1000+
> cycles. So
On Tue, May 15, 2018 at 09:49:06PM -0700, Srinivas Pandruvada wrote:
> When a task is woken up from IO wait, boost HWP prformance to max. This
> helps IO workloads on servers with per core P-states. But changing limits
> has extra over head of issuing new HWP Request MSR, which takes 1000+
>
On Tue, May 15, 2018 at 09:49:06PM -0700, Srinivas Pandruvada wrote:
> When a task is woken up from IO wait, boost HWP prformance to max. This
> helps IO workloads on servers with per core P-states. But changing limits
> has extra over head of issuing new HWP Request MSR, which takes 1000+
>
When a task is woken up from IO wait, boost HWP prformance to max. This
helps IO workloads on servers with per core P-states. But changing limits
has extra over head of issuing new HWP Request MSR, which takes 1000+
cycles. So this change limits setting HWP Request MSR. Also request can
be for a
When a task is woken up from IO wait, boost HWP prformance to max. This
helps IO workloads on servers with per core P-states. But changing limits
has extra over head of issuing new HWP Request MSR, which takes 1000+
cycles. So this change limits setting HWP Request MSR. Also request can
be for a
12 matches
Mail list logo