linux-kernel - Re: IRQ affinities (was: boot cgroup questions)

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: <20080509070314.f86aece4.pj@sgi.com>
Date:	Fri, 9 May 2008 07:03:14 -0500
From:	Paul Jackson <pj@....com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	maxk@...lcomm.com, menage@...gle.com, mingo@...e.hu,
	linux-kernel@...r.kernel.org
Subject: Re: IRQ affinities (was: boot cgroup questions)

Peter wrote:
> I see two use-cases:
> 
>  - Isolation
>  - NUMA node devices

Ok ... so let me propose an entirely different solution.

No doubt it has some terrible flaw, but I'll just have to
await your replies to see what that is.

How about we have:

 1) Yet another text config file in /etc, this one containing
    lines having two fields:
	* a list of IRQs, and
	* a cpumask.
    This file would specify which CPUs should handle which IRQs.

 2) A utility that can be run, after changing the above file, 
    to poke the proper cpumask to each IRQ, as specified in
    the file.

(Obligatory "simple" marketing claim: the above requires no
kernel changes.)

What am I missing?

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.940.382.4214
--
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/