linux-kernel - Re: [PATCH 5/5] Only call rebalance_domains when needed from scheduler

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: <4540A986.2070200@yahoo.com.au>
Date:	Thu, 26 Oct 2006 22:26:46 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Christoph Lameter <clameter@....com>
CC:	akpm@...l.org, Peter Williams <pwil3058@...pond.net.au>,
	linux-kernel@...r.kernel.org,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Dave Chinner <dgc@....com>, Ingo Molnar <mingo@...e.hu>,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>
Subject: Re: [PATCH 5/5] Only call rebalance_domains when needed from scheduler_tick

Christoph Lameter wrote:
> Only call rebalance_domains when needed from scheduler_tick.
> 
> Call rebalance_domains from a tasklet with interrupt enabled.
> Only call it when one of the sched domains is to be rebalanced.
> The jiffies when the next balancing action is to take place is
> kept in a per cpu variable next_balance.

sched-domains was supposed to be able to build a whacky topology
so you didn't have to take the occasional big latency hit when
scanning 512 CPUs...

Ideas were: overlapping, non-covering top level domains, or a
SD_BALANCE_ROTOR, which scans only N (< all) groups on each
balance attempt, but more frequently.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 
-
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/