On Tue, 31 Jul 2018 at 05:32, Wanpeng Li wrote:
> > > >
> > > > #if defined(CONFIG_IRQ_TIME_ACCOUNTING) ||
> > > > defined(CONFIG_PARAVIRT_TIME_ACCOUNTING)
> > > > if ((irq_delta + steal) && sched_feat(NONTASK_CAPACITY))
> > > > - sched_rt_avg_update(rq, irq_delta + steal)
On Tue, 31 Jul 2018 at 00:43, Vincent Guittot
wrote:
>
> Hi Wanpeng,
>
> On Thu, 26 Jul 2018 at 05:09, Wanpeng Li wrote:
> >
> > Hi Vincent,
> > On Fri, 29 Jun 2018 at 03:07, Vincent Guittot
> > wrote:
> > >
> > > interrupt and steal time are the only remaining activities tracked by
> > > rt_avg
Hi Wanpeng,
On Thu, 26 Jul 2018 at 05:09, Wanpeng Li wrote:
>
> Hi Vincent,
> On Fri, 29 Jun 2018 at 03:07, Vincent Guittot
> wrote:
> >
> > interrupt and steal time are the only remaining activities tracked by
> > rt_avg. Like for sched classes, we can use PELT to track their average
> > utiliz
Hi Vincent,
On Fri, 29 Jun 2018 at 03:07, Vincent Guittot
wrote:
>
> interrupt and steal time are the only remaining activities tracked by
> rt_avg. Like for sched classes, we can use PELT to track their average
> utilization of the CPU. But unlike sched class, we don't track when
> entering/leavi
interrupt and steal time are the only remaining activities tracked by
rt_avg. Like for sched classes, we can use PELT to track their average
utilization of the CPU. But unlike sched class, we don't track when
entering/leaving interrupt; Instead, we take into account the time spent
under interrupt c
5 matches
Mail list logo