* bnx2, 2.6.29, smp_affinity strangeness
@ 2009-03-29 1:47 Denys Fedoryschenko
2009-03-29 2:27 ` Denys Fedoryschenko
2009-04-03 5:26 ` Michael Chan
0 siblings, 2 replies; 4+ messages in thread
From: Denys Fedoryschenko @ 2009-03-29 1:47 UTC (permalink / raw)
To: netdev
Hi
While running bnx2 tried to assign affinity to network card and ... failed.
Here it is:
globax2 ~ # cat /proc/interrupts |grep
eth1;cat /proc/irq/97/smp_affinity ;sleep 4;cat /proc/interrupts |grep eth1
97: 5637762 5637764 5637745 5637674 5637815 5637842
5637795 5637839 PCI-MSI-edge eth1
10
97: 5641756 5641754 5641739 5641669 5641809 5641836
5641789 5641833 PCI-MSI-edge eth1
As you see, smp_affinity set to CPU4 (5th CPU if count from 1), but interrupts
is still happening on all CPU's.
Meanwhile i found more strange things:
I did ifconfig to eth0 up
in dmesg got
[ 4855.804365] bnx2 0000:05:00.0: irq 98 for MSI/MSI-X
[ 4855.923017] bnx2: eth0: using MSI
default_smp_affinity was 0xf (first 4 CPU)
and got:
98: 66 73 67 67 0 0
0 0 PCI-MSI-edge eth0
but if i try to change smp_affinity while it is running - it wont change
anything.
If i bring interface down, i will see strange entry
98: 90 90 86 88 0 0
0 0 none-<NULL>
Now i have entry in /proc/irq/98/ , so while it is down i change affinity to
10. Voila, i bring it up, and affinity working correct.
98: 90 90 86 88 51 0
0 0 PCI-MSI-edge eth0
98: 90 90 86 88 129 0
0 0 PCI-MSI-edge eth0
Is it correct that i am able to change IRQ affinity only when interface down?
On other cards i can change it "on fly".
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: bnx2, 2.6.29, smp_affinity strangeness
2009-03-29 1:47 bnx2, 2.6.29, smp_affinity strangeness Denys Fedoryschenko
@ 2009-03-29 2:27 ` Denys Fedoryschenko
2009-03-29 2:35 ` Eric Dumazet
2009-04-03 5:26 ` Michael Chan
1 sibling, 1 reply; 4+ messages in thread
From: Denys Fedoryschenko @ 2009-03-29 2:27 UTC (permalink / raw)
To: netdev
Forgot to tell
kernel 2.6.29 x86_64
userspace is 32-bit
I test also 32-bit kernel/32-bit userspace - same result.
On Sunday 29 March 2009 04:47:58 Denys Fedoryschenko wrote:
> While running bnx2 tried to assign affinity to network card and ... failed.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: bnx2, 2.6.29, smp_affinity strangeness
2009-03-29 1:47 bnx2, 2.6.29, smp_affinity strangeness Denys Fedoryschenko
2009-03-29 2:27 ` Denys Fedoryschenko
@ 2009-04-03 5:26 ` Michael Chan
1 sibling, 0 replies; 4+ messages in thread
From: Michael Chan @ 2009-04-03 5:26 UTC (permalink / raw)
To: 'Denys Fedoryschenko', netdev@vger•kernel.org
Denys Fedoryschenko wrote:
> While running bnx2 tried to assign affinity to network card
> and ... failed.
>
This is a known problem on the 5708 card that does not support
MSI per vector masking. On the 5708 NIC, the new MSI address/
data will only take effect after MSI has been disabled and
re-enabled.
The IRQ migration code in the kernel no longer disables the MSI
on devices that don't support per masking before IRQ migration.
As a result, changing IRQ affinity will not work after the device
is initialized. You can force a reset, (by doing some ethtool
operation for example), after you change the affinity and it should
work.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-04-03 5:26 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-29 1:47 bnx2, 2.6.29, smp_affinity strangeness Denys Fedoryschenko
2009-03-29 2:27 ` Denys Fedoryschenko
2009-03-29 2:35 ` Eric Dumazet
2009-04-03 5:26 ` Michael Chan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox