linux-kernel - Re: [PATCH] cpumask: convert cpumask_of_cpu() with cpumask

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 30 May 2011 10:40:07 +0900
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	a.p.zijlstra@...llo.nl
CC:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	efault@....de, mingo@...e.hu
Subject: Re: [PATCH] cpumask: convert cpumask_of_cpu() with cpumask_of()

>> The trick is,
>>  - Typical linux userland applications don't use mempolicy and/or cpusets
>>    API at all.
>>  - Then, 99.99% thread's  tsk->cpus_alloed have cpu_all_mask.
>>  - cpu_all_mask case, every thread can share the same bitmap. It may help to
>>    reduce L1 cache miss in scheduler.
>>
>> What do you think? 
> 
> Nice!
> 
> If you finish the first patch (sort the TODOs) I'll take it.

Yeah, now I'm submitting a lot of cpumask cleanup patches to various arch and
subsystems. So, I expect I can finish this work in June.

> I'm unsure about the PF_THREAD_UNBOUND thing though, then again, the
> alternative is adding another struct cpumask * and have that point to
> the shared mask or the private mask.

Ahhh, I'm sorry. My explanation was bad. PF_THREAD_UNBOUND is not my point.
It's only concept proof patch, not for submitting. yes, I did cheat for getting
number easily. I think the good way is probably to add another cpumask* and
implement COW shared mask. but I'm ok other way too.


> But yeah, looks quite feasible.

Thank you to pay attention my patch!

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