2009ÄêÇï¼¾(µÚ74½ì)Öйúµç×ÓÕ¹
74th China Electronics Fair (74th CEF)
ôß2009Öйú(ÉϺ£)¹ú¼Êµç×ÓÕ¹ÀÀ»á
2009 International Electronics Expo ( IEE Shanghai 2009)
ÉϺ£Ð¹ú¼Ê²©ÀÀÖÐÐÄ
2009Äê11ÔÂ11ÈÕ-13ÈÕ
Öйúµç×ÓÕ¹£¨CEF£©
ÐÅÏ¢»¯Íƶ¯¹¤Òµ»¯£¬µç×Ó¼¼Êõ´Ù½ø²úÒµÉý¼¶
Ö÷°ìµ¥Î»:
Öйúµç×ÓÆ÷²Ä×ܹ«Ë¾
³Ð°ìµ¥Î»:
Hi there,
I'm still evaluating RSS feature of Intel 82598EB AF 10G ethernet card.
I think this is my last problem.
that is computed hash value of NIC.
Before the evaluation, I wrote a simulation code to simulate ComputeHash
function according to datasheet.
and I checked it by RSS verification sui
Thank you Jesse,
> you also apparently are not using MSI interrupts.
No. I can see the kernel messages below in syslog.
In the kernel options, I found APIC related items and MSI are disabled.
kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.5.18.3
kernel: e1000e: Copyright(c) 1999 - 2009 Int
Thank you John,
> Is the interrupt shared with other devices? Do things work
> correctly with a newer kernel? What kind of system is this?
Yes, the interrupts are shared with each devices.
IOAPIC and MSI are disabled by kernel options.
I have used only 2.6.10 and not tried the newer kernel yet
On Wed, 1 Jul 2009, Yosuke HIZUME wrote:
> I'm using e1000e-0.5.8.13 *Non-NAPI* on kernel 2.6.10 with 82573L.
> I found the receiving data was occasionally corrupted just after I
> changed the mtu or the speed and duplex setting.
you also apparently are not using MSI interrupts.
> Then I inserte
On Mon, 8 Jun 2009, Lal wrote:
> >> I am using 2.6.21 kernel and CONFIG_E1000_NAPI is defined. It's a
> >> multi-core system.
> >>
> >> In e1000_intr the interface, over which packet is received, is queued
> >> in poll_list (per cpu based).
> >
> > this is the key.
> >
> >> Later net_rx_action invo
Just FYI, our development tree is internal only for our out of tree driver, but
we send patches to the kernel ASAP, after they have passed testing.
-Original Message-
From: Nix [mailto:n...@esperi.org.uk]
Sent: Saturday, June 06, 2009 9:46 AM
To: Waskiewicz Jr, Peter P
Cc: e1000-devel@li
Is the interrupt shared with other devices? Do things work correctly with a
newer kernel? What kind of system is this?
Cheers,
John
---
"...that your people will judge you on what you can build, not what you
destroy.", B. Obama, 2009
2009ÄêÇï¼¾(µÚ74½ì)Öйúµç×ÓÕ¹
74th China Electronics Fair (74th CEF)
ôß2009Öйú(ÉϺ£)¹ú¼Êµç×ÓÕ¹ÀÀ»á
2009 International Electronics Expo ( IEE Shanghai 2009)
ÉϺ£Ð¹ú¼Ê²©ÀÀÖÐÐÄ
2009Äê11ÔÂ11ÈÕ-13ÈÕ
Öйúµç×ÓÕ¹£¨CEF£©
ÐÅÏ¢»¯Íƶ¯¹¤Òµ»¯£¬µç×Ó¼¼Êõ´Ù½ø²úÒµÉý¼¶
Ö÷°ìµ¥Î»:
Öйúµç×ÓÆ÷²Ä×ܹ«Ë¾
³Ð°ìµ¥Î»:
Dear experts,
I'm using e1000e-0.5.8.13 *Non-NAPI* on kernel 2.6.10 with 82573L.
I found the receiving data was occasionally corrupted just after I
changed the mtu or the speed and duplex setting.
Then I inserted some printk codes to investigate and found that
e1000_intr() was infrequently called
10 matches
Mail list logo
