linux-kernel - Re: [PATCH 1/2] Customize sched domain via cpuset

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080403081411.aae6a064.pj@sgi.com>
Date:	Thu, 3 Apr 2008 08:14:11 -0500
From:	Paul Jackson <pj@....com>
To:	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, peterz@...radead.org,
	andi@...stfloor.org
Subject: Re: [PATCH 1/2] Customize sched domain via cpuset

H.Seto wrote:
> I believe there are quite technical reasons why we have no "idle_map."

I would not advocate a single system wide cpumask of idle CPUs.  As
Peter Zijlstra notes in a follow up post, that's too hot a cache line
and clearly doesn't scale.

But I would think it would be ok to have a separate cpumask per node,
that marked just the node-local CPUs.  We have other per-node data
already.  If we only support this optional load balancing level across
the other CPUs on the same node (or smaller domains, such as the cores
in a package), that should work, shouldn't it?

> so I'll update my patch to take levels, getting in your suggestion.

If you see a good solution here that you can provide, good.  But if my
brain storming ideas have problems, don't hesitate to object to them.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.940.382.4214
--
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/