netdev - Re: new NAPI interface broken for POWER architecture?

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: <200709121718.37820.ARNDB@de.ibm.com>
Date:	Wed, 12 Sep 2007 17:18:36 +0200
From:	Arnd Bergmann <ARNDB@...ibm.com>
To:	Christoph Raisch <RAISCH@...ibm.com>
Cc:	David Miller <davem@...emloft.net>,
	Jan-Bernd Themann <THEMANN@...ibm.com>, netdev@...r.kernel.org,
	ossthema@...ux.vnet.ibm.com, shemminger@...ux-foundation.org,
	Paul Mackerras <pmac@....ibm.com>,
	Michael Ellerman <ellerman@....ibm.com>,
	linuxppc-dev@...abs.org
Subject: Re: new NAPI interface broken for POWER architecture?

On Wednesday 12 September 2007, Christoph Raisch wrote:
> David Miller <davem@...emloft.net> wrote on 12.09.2007 14:50:04:
>
> > I agree that it should be fixed, but we should also fix the IRQ
> > distribution scheme used on powerpc platforms which is totally
> > broken in these cases.
> 
> This is definitely not something we can change in the HEA device driver
> alone.
> It could also affect any other networking cards on POWER (e1000,s2io...).
> 
> Paul, Michael, Arndt, what is your opinion here?

The situation on Cell with the existing south bridge chips is that
interrupts _never_ get moved around, but are routed to specific
SMT threads by the firmware, while Linux does not interfere with
this.

We have been thinking about changing this so we can distribute
interrupts over all SMT threads in a given NUMA node, or even
over all logical CPUs in the system by reprogramming the
interrupt controller after each interrupt, but the current Axon bridge
chip will always have all devices routed to the same target CPU,
so it's unclear whether that is even an advantage.

	Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html