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
| ||
|
Message-ID: <20130103022911.GH11220@mtj.dyndns.org> Date: Wed, 2 Jan 2013 21:29:11 -0500 From: Tejun Heo <tj@...nel.org> To: Rusty Russell <rusty@...tcorp.com.au> Cc: Li Zefan <lizefan@...wei.com>, paul@...lmenage.org, glommer@...allels.com, containers@...ts.linux-foundation.org, cgroups@...r.kernel.org, peterz@...radead.org, mhocko@...e.cz, bsingharora@...il.com, hannes@...xchg.org, kamezawa.hiroyu@...fujitsu.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 06/13] cpuset: cleanup cpuset[_can]_attach() Hello, Rusty. On Thu, Jan 03, 2013 at 11:17:11AM +1030, Rusty Russell wrote: > > So, I guess this currently is caught in a place which isn't here or > > there. I'm pretty skeptical whether it makes sense to bother about > > static usages tho. Can I keep them for static ones? > > I didn't realize that cpuset_attach was a fastpath. If it is, put a It isn't a hot path. It's just a bit nasty to have to allocate them separately. > static there and I'll fix turn it into a bitmap when I need to. > Otherwise, please don't change the code in the first place. So, the plan to drop cpumask_t is still on? If so, I'll leave cpumask_var_t. Thanks. -- tejun -- 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