lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 17 Sep 2015 10:31:41 +0800 From: Yuyang Du <yuyang.du@...el.com> To: bsegall@...gle.com Cc: Morten Rasmussen <morten.rasmussen@....com>, Peter Zijlstra <peterz@...radead.org>, Dietmar Eggemann <dietmar.eggemann@....com>, Vincent Guittot <vincent.guittot@...aro.org>, Steve Muckle <steve.muckle@...aro.org>, "mingo@...hat.com" <mingo@...hat.com>, "daniel.lezcano@...aro.org" <daniel.lezcano@...aro.org>, "mturquette@...libre.com" <mturquette@...libre.com>, "rjw@...ysocki.net" <rjw@...ysocki.net>, Juri Lelli <Juri.Lelli@....com>, "sgurrappadi@...dia.com" <sgurrappadi@...dia.com>, "pang.xunlei@....com.cn" <pang.xunlei@....com.cn>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 5/6] sched/fair: Get rid of scaling utilization by capacity_orig On Wed, Sep 16, 2015 at 10:06:24AM -0700, bsegall@...gle.com wrote: > > The point really is, metrics (if not many ) need resolution, not just NICE_0_LOAD does. > > You can choose to either hardcode a number, like SCHED_CAPACITY_SHIFT now, > > or you can use SCHED_RESOLUTION_SHIFT, which is even as simple as a sign to say what > > the defined is (the scaled one with a better resolution vs. the original one). > > I guess this is to say we now have a (no-big-deal) resolution system. > > Yes they were chosen for similar reasons, but they are not conceptually > related, and you couldn't decide to just bump up all the resolutions by > changing SCHED_RESOLUTION_SHIFT, so doing this would just be misleading. Yes, it appears they are made seemingly conceptually related. But probably it isn't worth a concern, if one knows it is just a scaled integer metric. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists