Kernel 2.6.12-rc6-mm1 & Chelsio driver
Hello,
should chelsio 10GE driver work in this kernel? If I do modprobe cxgb, then it silently returns. No messages in log (dmesg) nor terminal and no new ethX device is discoverred.
Signature · 1 line
Lukáš Hejtmánek
Quoted 4 lines · Lukas Hejtmanek
Hello,
should chelsio 10GE driver work in this kernel? If I do modprobe cxgb, then it silently returns. No messages in log (dmesg) nor terminal and no new ethX device is discoverred.
I suppose you have Chelsio hardware?
Jeff
Quoted 6 lines · Jeff Garzik
Quoted 4 lines
should chelsio 10GE driver work in this kernel? If I do modprobe cxgb, then it
silently returns. No messages in log (dmesg) nor terminal and no new ethX device is discoverred.I suppose you have Chelsio hardware?
Yes :)
Bus 2, device 3, function 0:
Ethernet controller: PCI device 1425:0006 (ASIC Designers Inc) (rev 0).
IRQ 24.
Master Capable. Latency=248.
Non-prefetchable 64 bit memory at 0xf6042000 [0xf6042fff].
kernel 2.6.6 and driver from web site:
Chelsio TOE Network Driver - version 2.1.0
eth0: Chelsio T110 1x10GBaseX TOE (rev 1), PCIX 100MHz/64-bit
eth0: 512MB SDRAM, 128MB FCRAM
Signature · 1 line
Lukáš Hejtmánek
Quoted 17 lines · Lukas Hejtmanek
Quoted 4 lines · Jeff Garzik
Quoted 2 lines
should chelsio 10GE driver work in this kernel? If I do modprobe cxgb, then it silently returns. No messages in log (dmesg) nor terminal and no new ethX device is discoverred.
I suppose you have Chelsio hardware?
Yes :)
Bus 2, device 3, function 0:
Ethernet controller: PCI device 1425:0006 (ASIC Designers Inc) (rev 0).
IRQ 24.
Master Capable. Latency=248.
Non-prefetchable 64 bit memory at0xf6042000[0xf6042fff].
Quoted 4 lines
kernel 2.6.6 and driver from web site:
Chelsio TOE Network Driver - version 2.1.0
eth0: Chelsio T110 1x10GBaseX TOE (rev 1), PCIX 100MHz/64-bit
eth0: 512MB SDRAM, 128MB FCRAM
I can't help much beyond this then :( There should be Chelsio email addresses in the driver...
Jeff
Quoted 7 lines · Jeff Garzik
Quoted 7 lines
Bus 2, device 3, function 0:
Ethernet controller: PCI device 1425:0006 (ASIC Designers Inc) (rev 0).IRQ 24. Master Capable. Latency=248. Non-prefetchable 64 bit memory at 0xf6042000 [0xf6042fff].
Quoted 7 lines
Quoted 4 lines
kernel 2.6.6 and driver from web site:
Chelsio TOE Network Driver - version 2.1.0
eth0: Chelsio T110 1x10GBaseX TOE (rev 1), PCIX 100MHz/64-bit
eth0: 512MB SDRAM, 128MB FCRAMI can't help much beyond this then :( There should be Chelsio email addresses in the driver...
I'am afraid that they oficially support only 2.6.6 kernel :(
I wonder whether this driver works for someone. If not, it should be removed.
And also, who does it maintain?
Signature · 1 line
Lukáš Hejtmánek
Lukas Hejtmanek <[email protected]> :
[...]
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Ethernet controller: PCI device 1425:0006 (ASIC Designers Inc) (rev 0).
IRQ 24. Master Capable. Latency=248. Non-prefetchable 64 bit memory at 0xf6042000 [0xf6042fff].
/me greps in -mm
#define CH_DEVICE(devid, ssid, idx) \
{ PCI_VENDOR_ID_CHELSIO, devid, PCI_ANY_ID, ssid, 0, 0, idx }
[...]
enum {
CH_BRD_N110_1F,
CH_BRD_N210_1F,
CH_BRD_T210_1F,
};
[...]
struct pci_device_id t1_pci_tbl[] = {
CH_DEVICE(7, 0, CH_BRD_N110_1F),
CH_DEVICE(10, 1, CH_BRD_N210_1F),
{ 0, }
};-> it does not match your 0006 revision. No wonder nothing gets detected.
As a quick hack, one could cross fingers and add a CH_DEVICE(6, 0, CH_BRD_N110_1F)
or, if it does not work:
CH_DEVICE(6, 1, CH_BRD_N210_1F)
(the drivers code suggests some deep differences between CH_BRD_N210_1F and CH_BRD_N110_1F wrt irq management for instance)
If it does not work at all, someone will have to dissect the whole thing. Please fill an entry at bugzilla.kernel.org, add it your lspci info and make it link the 2.6.6 driver from Chelsio's website.
--
Ueimor
Quoted 8 lines · Francois Romieu
-> it does not match your 0006 revision. No wonder nothing gets detected.
As a quick hack, one could cross fingers and add a
CH_DEVICE(6, 0, CH_BRD_N110_1F)or, if it does not work:
CH_DEVICE(6, 1, CH_BRD_N210_1F)
I added:
enum {
CH_BRD_T110_1F,
CH_BRD_N110_1F,
CH_BRD_N210_1F,
CH_BRD_T210_1F,
};struct pci_device_id t1_pci_tbl[] = {
CH_DEVICE(6, 0, CH_BRD_T110_1F),
CH_DEVICE(6, 1, CH_BRD_T110_1F),
CH_DEVICE(7, 0, CH_BRD_N110_1F),
CH_DEVICE(10, 1, CH_BRD_N210_1F),
{ 0, }
};according to 2.6.6 driver.
However, it seems to be highly unstable. Using iperf it gets broken. Card receives packets but it does not transmit after some iperf tests.
Using tcpdump I see things like this:
tcpdump -ni eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 23:05:03.854587 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 1 23:05:04.853853 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 2 23:05:05.853965 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 3 23:05:06.854079 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 4 23:05:07.854193 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 5
Quoted 3 lines
If it does not work at all, someone will have to dissect the whole thing. Please fill an entry at bugzilla.kernel.org, add it your lspci info and make it link the 2.6.6 driver from Chelsio's website.
Should I still add an bugzilla entry? Unfortunately, 2.6.6. driver from website is accessible only through password.
Signature · 1 line
Lukáš Hejtmánek
Lukas Hejtmanek <[email protected]> :
[...]
Quoted 2 lines
However, it seems to be highly unstable. Using iperf it gets broken. Card receives packets but it does not transmit after some iperf tests.
Hard to tell without further investigation if there is some kind of wraparound or some unordered acesses to the asic (or worse).
[...]
Quoted 2 lines
Should I still add an bugzilla entry? Unfortunately, 2.6.6. driver from website is accessible only through password.
Is it available under anything like a GPL license ?
--
Ueimor
Hi Lukas,
It looks like you have a T110 card (10Gb TOE) by the device ID 0006.
The Chelsio driver which is in the 2.6 mm tree only supports the NIC model cards (N110 & N210).
We currently don't have the TOE API in the Linux kernel so the TOE functionality does not exist, therefore you can only use the Chelsio modified 2.6.6 kernel for TOE.
You will need to download the driver from Chelsio's website for the T110. Please send me an email if you don't have a login.
Thanks,
Scott Bardone
Chelsio Communications
http://www.chelsio.com
Quoted 53 lines · Lukas Hejtmanek
Quoted 8 lines · Francois Romieu
-> it does not match your 0006 revision. No wonder nothing gets detected.
As a quick hack, one could cross fingers and add a
CH_DEVICE(6, 0, CH_BRD_N110_1F)or, if it does not work:
CH_DEVICE(6, 1, CH_BRD_N210_1F)I added:
enum { CH_BRD_T110_1F, CH_BRD_N110_1F, CH_BRD_N210_1F, CH_BRD_T210_1F, };struct pci_device_id t1_pci_tbl[] = { CH_DEVICE(6, 0, CH_BRD_T110_1F), CH_DEVICE(6, 1, CH_BRD_T110_1F), CH_DEVICE(7, 0, CH_BRD_N110_1F), CH_DEVICE(10, 1, CH_BRD_N210_1F), { 0, } };according to 2.6.6 driver.
However, it seems to be highly unstable. Using iperf it gets broken. Card receives packets but it does not transmit after some iperf tests.
Using tcpdump I see things like this:
tcpdump -ni eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 23:05:03.854587 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 1 23:05:04.853853 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 2 23:05:05.853965 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 3 23:05:06.854079 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 4 23:05:07.854193 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 5Quoted 3 lines
If it does not work at all, someone will have to dissect the whole thing. Please fill an entry at bugzilla.kernel.org, add it your lspci info and make it link the 2.6.6 driver from Chelsio's website.
Should I still add an bugzilla entry? Unfortunately, 2.6.6. driver from website is accessible only through password.
Quoted 10 lines · Scott Bardone
It looks like you have a T110 card (10Gb TOE) by the device ID 0006. The Chelsio driver which is in the 2.6 mm tree only supports the NIC model cards (N110 & N210).
We currently don't have the TOE API in the Linux kernel so the TOE functionality does not exist, therefore you can only use the Chelsio modified 2.6.6 kernel for TOE.
You will need to download the driver from Chelsio's website for the T110. Please send me an email if you don't have a login.
Thanks, we have an account. But I wonder whether T110 card could be used in newer kernel (as 2.6.6 is rather old and cat /proc/iomap segfaults in kernel).
We do not need TOE functionality, UDP transfer is just fine.
Signature · 1 line
Lukáš Hejtmánek
Quoted 3 lines · Scott Bardone
We currently don't have the TOE API in the Linux kernel so the TOE functionality does not exist, therefore you can only use the Chelsio modified 2.6.6 kernel for TOE.
Care to explain what modifications you do, and whether or not you consider your card firmware a derived work of the TCP stack because of them?
We modify the existing Linux TCP stack to add "hooks" so that our card can perform TCP offload and HW based checksum, thus making it possible to see high throughput with multiple connections and low CPU utilization.
We add 2 source files to the kernel, toedev.c and offload.c. We also modify neighbor.c, tcp.c, tcp_diag.c, tcp_ipv4.c, tcp_timer.c to add functions for our TOE capabilities so that the offloaded packet can be sent to our hardware (offload) path instead of going through the software (TCP stack) path.
Our processing engine is an ASIC with a HW based TCP stack which processes packets with Chelsio's CPL messages (Chelsio Protocol Language). I would not consider it a derived work.
-Scott
Quoted 8 lines · Christoph Hellwig
Quoted 1 line · Scott Bardone
We currently don't have the TOE API in the Linux kernel so the TOE functionality does not exist, therefore you can only use the Chelsio modified 2.6.6 kernel for TOE.
Care to explain what modifications you do, and whether or not you consider your card firmware a derived work of the TCP stack because of them?