| 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
| ||
|
Date: Fri, 09 May 2008 16:33:37 -0700 From: Rick Jones <rick.jones2@...com> To: Jesper Krogh <jesper@...gh.cc> CC: David Miller <davem@...emloft.net>, yhlu.kernel@...il.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: NIU - Sun Neptune 10g - Transmit timed out reset (2.6.24) Jesper Krogh wrote: > Rick Jones wrote: > >>>> To which cpu(s) were the neptune's interrupts assigned? (grep <ethN> >>>> /proc/interrupts) >>> >>> >>> Several >> >> >> Which ones?-) I suspect that since it is several that at least >> answers the MSI_X question right? Or is it possible to have a single >> device have several MSI interrupts? Well, the output below anwered my question about multiple MSI's from a single device :) > > > The table is rather large. > http://rafb.net/p/a9zfFA59.html So, over time at least, the interrupts have been spread over half the cores in the system. This is where the block diagram showing the socket and I/O slot connections would be useful. For the interrupts over a given interval, one can take snapshots at either end of the interval and then run them through beforeafter: ftp://ftp.cup.hp.com/dist/networking/tools/ I think that collectl might have something there too. I guess the addresses in use weren't sufficient to get interrupts spread across all 24 IRQ's. rick jones -- 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
Powered by blists - more mailing lists