linux-kernel - Re: [RFC/PATCH] cpuset: cpuset irq affinities

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 7 Mar 2008 00:47:54 -0800
From:	"Paul Menage" <menage@...gle.com>
To:	"Paul Jackson" <pj@....com>
Cc:	a.p.zijlstra@...llo.nl, maxk@...lcomm.com, mingo@...e.hu,
	tglx@...utronix.de, oleg@...sign.ru, rostedt@...dmis.org,
	linux-kernel@...r.kernel.org, rientjes@...gle.com
Subject: Re: [RFC/PATCH] cpuset: cpuset irq affinities

On Thu, Mar 6, 2008 at 10:39 PM, Paul Jackson <pj@....com> wrote:
>  I guess this will require adding a line:
>         .create = cgroup_create
>  line to the:
>         static struct file_operations cgroup_file_operations = {
>  initialization in kernel/cgroup.c, and a cgroup_create() routine
>  in kernel/cgroup.c, that calls an optional per-cgroup-subsystem
>  create routine, that, in the case of cpusets, is willing to create
>  one of these irqs.N.name files, in the top cpuset, if all looks
>  right.
>

An alternative would be to just have some kind of "irqsets" file in
the top-level cpuset directory and let the user write irq group
definitions into that file.

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