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] [day] [month] [year] [list]
Date:	Thu, 10 Jan 2008 10:31:58 -0800
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Jeba Anandhan <jeba.anandhan@...oni.com>,
	Eric Dumazet <dada1@...mosbay.com>, netdev@...r.kernel.org,
	matthew.hattersley@...oni.com
Subject: Re: SMP code / network stack

Arnaldo Carvalho de Melo wrote:
> Em Thu, Jan 10, 2008 at 03:26:59PM +0000, Jeba Anandhan escreveu:
>> Hi Eric,
>> Thanks for the reply. I have one more doubt. For example, if we have 2
>> processor and 4 ethernet cards. Only CPU0 does all work through 8 cards.
>> If we set the affinity to each ethernet card as CPU number, will it be
>> efficient?.
>>
>> Will this be default behavior?
>>
>> # cat /proc/interrupts 
>>            CPU0       CPU1       
>>   0:   11472559   74291833    IO-APIC-edge  timer
>>   2:          0          0          XT-PIC  cascade
>>   8:          0          1    IO-APIC-edge  rtc
>>  81:          0          0   IO-APIC-level  ohci_hcd
>>  97: 1830022231        847   IO-APIC-level  ehci_hcd, eth0
>>  97: 3830012232        847   IO-APIC-level  ehci_hcd, eth1
>>  97: 5830052231        847   IO-APIC-level  ehci_hcd, eth2
>>  97: 6830032213        847   IO-APIC-level  ehci_hcd, eth3

another thing to try: if you don't need usb2 support, remove the ehci_hcd module -
this will give a slight less overhead servicing irq's in your system.

I take it that you have no MSI support in these ethernet cards?

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ