[request-sponsor] Tehuti OpenSolaris drivers
Hello, I've submitted a bug/RFE with Synopsis Tehuti 10GbE support in OpenSolaris. We have a year old ALPHA quality GLDv3 based driver, which was tested on SunOS 5.10 Generic_Patch_118844-30 powered by amd64. We produced the driver based on Nevada b40 GLDv3 header file using Sun C 5.7 Patch 117837-04 compiler. The driver provides fully functional full duplex TCP/IP network interface. The release is stable enough to support iperf stress tool. Solaris Driver Known Issues List: None what so ever? :) . VLAN hardware offload interface not implemented . Big Endian CPU architecture is not supported . Multicast filtering hardware offload interface not implemented . Only one port is supported . NDD Solaris management interface not implemented . RX performance is far from optimal Our main development platform is Linux and its driver provides all the mentioned missing features and good performance. The Linux driver is open source and could be used as reference implementation: http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.24.git;a=commitdiff; h=54406a1c0281af619e4d90bd7e719562be90216e We ready to release driver sources under CDDL license and it could be cool if Tehuti driver could be a part of OpenSolaris base distribution. Thank you, Alexander Indenbaum -- next part -- An HTML attachment was scrubbed... URL: http://mail.opensolaris.org/pipermail/request-sponsor/attachments/20070925/28afae8b/attachment.html
[request-sponsor] Tehuti OpenSolaris drivers
Once I know the CR number (which has yet to be assigned, due to the way the triage system works, which mere mortals like myself don't fully understand...) I'll be happy to act as your sponsor for this case. You should get an e-mail message in the next day or two with the CR number. Please respond with the CR number, and then we'll have to get you added to the list of outstanding CRs. Also, you'll need to know your Sun Contributor Agreement number. As I understand that you have faxed it in, you need to get back the number. Once you have got a response from that, please let us know your SCA# as well as the CR #. Thanks. -- Garrett Alexander Indenbaum wrote: Hello, I've submitted a bug/RFE with Synopsis Tehuti 10GbE support in OpenSolaris. We have a year old ALPHA quality GLDv3 based driver, which was tested on SunOS 5.10 Generic_Patch_118844-30 powered by amd64. We produced the driver based on Nevada b40 GLDv3 header file using Sun C 5.7 Patch 117837-04 compiler. The driver provides fully functional full duplex TCP/IP network interface. The release is stable enough to support iperf stress tool. Solaris Driver Known Issues List: None what so ever? :) ? VLAN hardware offload interface not implemented ? Big Endian CPU architecture is not supported ? Multicast filtering hardware offload interface not implemented ? Only one port is supported ? NDD Solaris management interface not implemented ? RX performance is far from optimal Our main development platform is Linux and its driver provides all the mentioned missing features and good performance. The Linux driver is open source and could be used as reference implementation: http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.24.git;a=commitdiff;h=54406a1c0281af619e4d90bd7e719562be90216e We ready to release driver sources under CDDL license and it could be cool if Tehuti driver could be a part of OpenSolaris base distribution. Thank you, Alexander Indenbaum
[request-sponsor] Tehuti OpenSolaris drivers
Garrett, I'll get back to you with the tracking numbers as soon as I get those. I'm pretty clear with Sun Contributor Agreement number since I faxed it and expect human intervention to finish the process. Is there any way to track the progress? I'm a little bit confused about CR# though. I expected to get id upon bug submission, but I got success message from web GUI without any id. Is it normal? Should I resubmit the bug once I have Sun Contributor Agreement number? Alexander Indenbaum -Original Message- From: Garrett D'Amore [mailto:garrett at damore.org] Sent: Tuesday, September 25, 2007 5:36 PM To: Alexander Indenbaum Cc: request-sponsor at opensolaris.org; 'Nick Bhavsar' Subject: Re: Tehuti OpenSolaris drivers Once I know the CR number (which has yet to be assigned, due to the way the triage system works, which mere mortals like myself don't fully understand...) I'll be happy to act as your sponsor for this case. You should get an e-mail message in the next day or two with the CR number. Please respond with the CR number, and then we'll have to get you added to the list of outstanding CRs. Also, you'll need to know your Sun Contributor Agreement number. As I understand that you have faxed it in, you need to get back the number. Once you have got a response from that, please let us know your SCA# as well as the CR #. Thanks. -- Garrett Alexander Indenbaum wrote: Hello, I've submitted a bug/RFE with Synopsis Tehuti 10GbE support in OpenSolaris. We have a year old ALPHA quality GLDv3 based driver, which was tested on SunOS 5.10 Generic_Patch_118844-30 powered by amd64. We produced the driver based on Nevada b40 GLDv3 header file using Sun C 5.7 Patch 117837-04 compiler. The driver provides fully functional full duplex TCP/IP network interface. The release is stable enough to support iperf stress tool. Solaris Driver Known Issues List: None what so ever? :) . VLAN hardware offload interface not implemented . Big Endian CPU architecture is not supported . Multicast filtering hardware offload interface not implemented . Only one port is supported . NDD Solaris management interface not implemented . RX performance is far from optimal Our main development platform is Linux and its driver provides all the mentioned missing features and good performance. The Linux driver is open source and could be used as reference implementation: http://git.kernel.org/?p=linux/kernel/git/davem/net- 2.6.24.git;a=commitdiff;h=54406a1c0281af619e4d90bd7e719562be90216e We ready to release driver sources under CDDL license and it could be cool if Tehuti driver could be a part of OpenSolaris base distribution. Thank you, Alexander Indenbaum
[request-sponsor] Tehuti OpenSolaris drivers
Alexander Indenbaum wrote: Garrett, I'll get back to you with the tracking numbers as soon as I get those. I'm pretty clear with Sun Contributor Agreement number since I faxed it and expect human intervention to finish the process. Is there any way to track the progress? Not that I know of. You could try e-mailing Bonnie Corwin. But at this point, I'd just sit tight for a day or two. If you've not heard back by Friday, then we'll escalate. I'm a little bit confused about CR# though. I expected to get id upon bug submission, but I got success message from web GUI without any id. Is it normal? Should I resubmit the bug once I have Sun Contributor Agreement number? No. Its normal and a result of the fact that there is an intermediate human step. Your initial submission goes into a triage queue, and a human checks it before filing a real bug on your behalf. Its an annoying artifact of the fact that bug tracking database is not public, and that we don't have a way to automatically vet CR submissions. You should get an e-mail response in a day or two. - Garrett Alexander Indenbaum -Original Message- From: Garrett D'Amore [mailto:garrett at damore.org] Sent: Tuesday, September 25, 2007 5:36 PM To: Alexander Indenbaum Cc: request-sponsor at opensolaris.org; 'Nick Bhavsar' Subject: Re: Tehuti OpenSolaris drivers Once I know the CR number (which has yet to be assigned, due to the way the triage system works, which mere mortals like myself don't fully understand...) I'll be happy to act as your sponsor for this case. You should get an e-mail message in the next day or two with the CR number. Please respond with the CR number, and then we'll have to get you added to the list of outstanding CRs. Also, you'll need to know your Sun Contributor Agreement number. As I understand that you have faxed it in, you need to get back the number. Once you have got a response from that, please let us know your SCA# as well as the CR #. Thanks. -- Garrett Alexander Indenbaum wrote: Hello, I've submitted a bug/RFE with Synopsis Tehuti 10GbE support in OpenSolaris. We have a year old ALPHA quality GLDv3 based driver, which was tested on SunOS 5.10 Generic_Patch_118844-30 powered by amd64. We produced the driver based on Nevada b40 GLDv3 header file using Sun C 5.7 Patch 117837-04 compiler. The driver provides fully functional full duplex TCP/IP network interface. The release is stable enough to support iperf stress tool. Solaris Driver Known Issues List: None what so ever? :) . VLAN hardware offload interface not implemented . Big Endian CPU architecture is not supported . Multicast filtering hardware offload interface not implemented . Only one port is supported . NDD Solaris management interface not implemented . RX performance is far from optimal Our main development platform is Linux and its driver provides all the mentioned missing features and good performance. The Linux driver is open source and could be used as reference implementation: http://git.kernel.org/?p=linux/kernel/git/davem/net- 2.6.24.git;a=commitdiff;h=54406a1c0281af619e4d90bd7e719562be90216e We ready to release driver sources under CDDL license and it could be cool if Tehuti driver could be a part of OpenSolaris base distribution. Thank you, Alexander Indenbaum
