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: <4614F56D.5020704@compro.net>
Date:	Thu, 05 Apr 2007 09:11:09 -0400
From:	Mark Hounschell <markh@...pro.net>
To:	Jiri Kosina <jikos@...os.cz>
CC:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: IRQ splitting

Jiri Kosina wrote:
> On Thu, 5 Apr 2007, Jan Engelhardt wrote:
> 
>> My question is whether it is possible that eth0's interrupts go to CPU0 
> 
> Documentation/IRQ-affinity.txt
> 

There is nothing in there tells ya how to get them off the same IRQ.
That has to be done first usually be moving one of them to another
slot/bus. Then Documentation/IRQ-affinity.txt can be referenced.

Somehow I think Jan already knew that and really wants to know
how to keep them from sharing the same irq without having to
change slot assignments. I know I would.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ