linux-kernel - Re: [RFC PATCH v1 1/2] sched: unified sched

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: <4F214380.2040601@kernel.dk>
Date:	Thu, 26 Jan 2012 13:13:52 +0100
From:	Jens Axboe <axboe@...nel.dk>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
CC:	Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>,
	Vincent Guittot <vincent.guittot@...aro.org>,
	Indan Zupancic <indan@....nu>,
	Youquan Song <youquan.song@...el.com>,
	Ingo Molnar <mingo@...e.hu>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v1 1/2] sched: unified sched_powersavings sysfs tunable

On 01/26/2012 01:04 PM, Peter Zijlstra wrote:
> On Thu, 2012-01-26 at 12:26 +0100, Jens Axboe wrote:
>> O
>> Yeah, I think that would suit my purpose nicely, in fact. What level of
>> cache sharing is being used here? The block code wanted a per-socket
>> type operation, but since it's a heuristic, perhaps the above is even
>> better (or equivelant, perhaps).
> 
> It uses the biggest shared cache exposed in the topology information the
> scheduler has (which is currently somewhat funny but is on the todo list
> for improvements).
> 
> Effectively it ends up being the socket wide LLC for modern Intel chips
> though.
> 
> Would something like the below work for you (compile tested only).

Yep, looks good to me, and an improvement for me not to carry this code
that doesn't really belong there.

-- 
Jens Axboe

--
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/