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: <514FBD6E.2030706@cn.fujitsu.com>
Date:	Mon, 25 Mar 2013 10:58:54 +0800
From:	Lin Feng <linfeng@...fujitsu.com>
To:	Lenky Gao <lenky.gao@...il.com>
CC:	linux-kernel@...r.kernel.org, yinghai@...nel.org, mingo@...e.hu,
	gorcunov@...il.com, rusty@...tcorp.com.au, sivanich@....com,
	agordeev@...hat.com
Subject: Re: Question: How to distribute the interrupts over multiple cores?

Hi Gao,

On 03/25/2013 10:33 AM, Lenky Gao wrote:
> [root@...alhost ~]# echo 6 > /proc/irq/25/smp_affinity
> [root@...alhost ~]# cat /proc/irq/25/smp_affinity
> 000006
Seems you bind the nic irq to second and third cpu for the bit mask
you set is 110, so now eth9's irq is working on the 3rd cpu.

Have you ever tried irqbalance service? It may help to balance irq if the 
irq workload of 3rd cpu is too heavy.

thanks,
linfeng
> [root@...alhost ~]# cat /proc/interrupts | grep eth9
>   25:       5824      13914        159        128        210
> 0          0          0  IR-IO-APIC-fasteoi   eth9
> [root@...alhost ~]# cat /proc/interrupts | grep eth9
>   25:       5824      13927        159        128        210
> 0          0          0  IR-IO-APIC-fasteoi   eth9
> [root@...alhost ~]# cat /proc/interrupts | grep eth9
>   25:       5824      13939        159        128        210
> 0          0          0  IR-IO-APIC-fasteoi   eth9
> [root@...alhost ~]# cat /proc/interrupts | grep eth9
>   25:       5824      13973        159        128        210
> 0          0          0  IR-IO-APIC-fasteoi   eth9
--
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