[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190927135259.GB3557@bug>
Date: Fri, 27 Sep 2019 15:53:00 +0200
From: Pavel Machek <pavel@....cz>
To: Parth Shah <parth@...ux.ibm.com>
Cc: Valentin Schneider <valentin.schneider@....com>,
Patrick Bellasi <patrick.bellasi@....com>,
linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
subhra mazumdar <subhra.mazumdar@...cle.com>,
tim.c.chen@...ux.intel.com, mingo@...hat.com,
morten.rasmussen@....com, dietmar.eggemann@....com, pjt@...gle.com,
vincent.guittot@...aro.org, quentin.perret@....com,
dhaval.giani@...cle.com, daniel.lezcano@...aro.org, tj@...nel.org,
rafael.j.wysocki@...el.com, qais.yousef@....com,
Patrick Bellasi <patrick.bellasi@...bug.net>
Subject: Re: Usecases for the per-task latency-nice attribute
Hi!
> > I don't want to start a bikeshedding session here, but I agree with Parth
> > on the interpretation of the values.
> >
> > I've always read niceness values as
> > -20 (least nice to the system / other processes)
> > +19 (most nice to the system / other processes)
> >
> > So following this trend I'd see for latency-nice:
>
>
> So jotting down separately, in case if we think to have "latency-nice"
> terminology, then we might need to select one of the 2 interpretation:
>
> 1).
> > -20 (least nice to latency, i.e. sacrifice latency for throughput)
> > +19 (most nice to latency, i.e. sacrifice throughput for latency)
> >
>
> 2).
> -20 (least nice to other task in terms of sacrificing latency, i.e.
> latency-sensitive)
> +19 (most nice to other tasks in terms of sacrificing latency, i.e.
> latency-forgoing)
For the record, interpretation 2 makes sense to me.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Powered by blists - more mailing lists