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-next>] [day] [month] [year] [list]
Date:	Mon, 01 Sep 2008 11:21:18 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Radu Rendec <radu.rendec@...s.ro>
CC:	linux-kernel@...r.kernel.org
Subject: Re: IRQ routing / assignment issue

Radu Rendec wrote:
> Hi,
> 
> I'm trying to make the kernel assign different irqs for two NICs
> connected to _separate_ pci buses. Messing around with pirq= kenrel
> parameter didn't seem to change anything.

The kernel doesn't really have any way to change the physical 
device/slot to IRQ mapping. In some cases there are BIOS settings which 
might influence this, but in most cases it's impossible to change (i.e. 
devices physically wired to the same IRQ line).

> 
> The machine is a smp (dual-xeon). Relevant lspci output is:
> 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721
> Gigabit Ethernet PCI Express (rev 11)
> 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721
> Gigabit Ethernet PCI Express (rev 11)
> 
> IRQ assignment dmesg output is:
> ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> 
> At the moment I'm almost clueless about how irq routing / assignment
> works (either in general or in linux), so any suggestion would help -
> even "rtfm" would be helpful, as long as you specify what is the
> appropriate manual ;)
> 
> If you are so kind to reply, please include my address in cc (I'm not
> subscribed).
> 
> Thanks,
> 
> Radu Rendec
> 
> 
> --
> 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/

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