| 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: Fri, 13 May 2011 11:14:47 +0200 From: Carl-Johan Kjellander <carl-johan@...rna.com> To: Peter Zijlstra <a.p.zijlstra@...llo.nl> Cc: Ingo Molnar <mingo@...e.hu>, Mike Galbraith <efault@....de>, Yong Zhang <yong.zhang0@...il.com>, linux-kernel@...r.kernel.org Subject: Re: Sched_autogroup and niced processes On Fri, May 13, 2011 at 11:07 AM, Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote: > On Fri, 2011-05-13 at 11:05 +0200, Ingo Molnar wrote: >> Could we somehow automate this: >> >> > echo 19 > /proc/'pid of seti@...e'/autogroup Tried this. echo 19 >/proc/23760/autogroup echo 1 > /proc/sys/kernel/sched_autogroup_enabled time make -j12 #seti@...e, autogroup, group reniced. real 3m9.274s user 11m3.020s sys 1m45.550s So 50% increase in compilation time. Will these autogroups remember the 19, the boinc manager starts 8 processes and it will spawn more as time goes by and it finishes tasks. >> and split off nice 19 tasks into separate groups and lower the group's >> priority? > > Well I guess you can stack on all kinds of heuristics, do we want to? > I'd argue for not, keep is simple. > I'd again argue, I use nice 19 for stuff that I want to run on the spare cycles, I don't want them stealing time from my important work or surfing or movie viewing. /cjk -- 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