Re: Heads UP - MFC for em coming shortly
At 04:36 PM 10/8/2007, Jack Vogel wrote: On 10/8/07, Mike Tancsa [EMAIL PROTECTED] wrote: At 04:28 PM 10/5/2007, Jack Vogel wrote: I am preparing to update the em driver to the equivalent of my 6.6.6 driver. Just doing some last minute sanity checking, I hope to the checkin before end of day. Hi, thanks for fixing the compile issue, but I have another possible problem. Do you know if there were any performance regressions with this rev? On one firewall / router, I am seeing dropped packets. The PPS rate is only about 30k which should not be that much So the missed packets are only showing up on em2? Uh, and that is a management-capable 82573, one that is often a problem without the eeprom patched, did you do that sometime in the past, I don't remember who did and who didnt :) Hi, I added the patch to the box in question. It would seem the NIC is not impacted by this bug em2: Excessive collisions = 0 em2: Sequence errors = 0 em2: Defer count = 0 em2: Missed Packets = 133 em2: Receive No Buffers = 41 em2: Receive Length Errors = 0 em2: Receive errors = 0 em2: Crc errors = 0 em2: Alignment errors = 0 em2: Collision/Carrier extension errors = 0 em2: RX overruns = 3 em2: watchdog timeouts = 0 em2: XON Rcvd = 0 em2: XON Xmtd = 0 em2: XOFF Rcvd = 0 em2: XOFF Xmtd = 0 em2: Good Packets Rcvd = 26550071 em2: Good Packets Xmtd = 14348973 em2: TSO Contexts Xmtd = 0 em2: TSO Contexts Failed = 0 Interface EEPROM Dump: Offset 0x 1500 2917 ef6f 0b30 f746 3017 0x0010 226b 348d 8086 108c 8086 acdf 0x0020 402d 2040 7e04 0200 00d8 2700 0x0030 6cc9 3150 072e 040b 0984 c000 0706 However, I am still seeing overruns on this interface at about 100Mb/s em2: Intel(R) PRO/1000 Network Connection Version - 6.6.6 port 0x2000-0x201f mem 0x8818-0x8819,0x8810-0x8817 irq 17 at device 0.0 on pci5 em2: Ethernet address: 00:15:17:29:6f:ef em2: [FAST] [EMAIL PROTECTED]:0:0: class=0x02 card=0x348d8086 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/1000 PM' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
At 12:37 AM 10/9/2007, Jack Vogel wrote: Thanks, I did find this reference http://www.higherorder.com.au/2007/6/25/intel_82573_patch Is there a way from FreeBSD to tell remotely if its needed ? Well, there would be a way, reading the MANC register and seeing if the suspect bit is present, but am not sure if there is some important point at which the thing gets misprogrammed, its just best to use the patcher, its harmless if its not needed. Sorry, I realize its a hassle to boot to that wonder DOS :) OK, did some tests on local PM nics here at the office. On one nic (same model as what is causing us problems in the field) we can run the program over and over again, and it always exits with a zero value. Is this normal ? On another NIC that we recently bought, it exits with a 1 which supposedly says not needed. How do we know that the update has taken ? Is there any danger of it losing its reprogramming ? In short, how do we verify it worked The version I am using is lava# ls -l dcgdis.exe -rw-r--r-- 1 root wheel 160029 Oct 4 2005 dcgdis.exe lava# md5 dcgdis.exe MD5 (dcgdis.exe) = a48d9e127c19528bd4a650e692b2f2be lava# Is there a newer one ? ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
On 10/9/07, Mike Tancsa [EMAIL PROTECTED] wrote: At 12:37 AM 10/9/2007, Jack Vogel wrote: Thanks, I did find this reference http://www.higherorder.com.au/2007/6/25/intel_82573_patch Is there a way from FreeBSD to tell remotely if its needed ? Well, there would be a way, reading the MANC register and seeing if the suspect bit is present, but am not sure if there is some important point at which the thing gets misprogrammed, its just best to use the patcher, its harmless if its not needed. Sorry, I realize its a hassle to boot to that wonder DOS :) OK, did some tests on local PM nics here at the office. On one nic (same model as what is causing us problems in the field) we can run the program over and over again, and it always exits with a zero value. Is this normal ? On another NIC that we recently bought, it exits with a 1 which supposedly says not needed. How do we know that the update has taken ? Is there any danger of it losing its reprogramming ? In short, how do we verify it worked The version I am using is lava# ls -l dcgdis.exe -rw-r--r-- 1 root wheel 160029 Oct 4 2005 dcgdis.exe lava# md5 dcgdis.exe MD5 (dcgdis.exe) = a48d9e127c19528bd4a650e692b2f2be lava# Is there a newer one ? There has only ever been one of these things, and its a binary wad to me just as to you, so I don't know why it returns success multple times, I guess it just checks the NIC type and does the write. People writing this are not Unix types, they are DOS tools programmers, should tell you something :) I was just talking to one of our Linux engineers and they actually export the ability to read and write the eeprom via ethtool, maybe I should look into adding something like a sysctl for that. Right now, just run it once, then test to see if the problem has disappeared. Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
At 04:28 PM 10/5/2007, Jack Vogel wrote: I am preparing to update the em driver to the equivalent of my 6.6.6 driver. Just doing some last minute sanity checking, I hope to the checkin before end of day. Hi, thanks for fixing the compile issue, but I have another possible problem. Do you know if there were any performance regressions with this rev? On one firewall / router, I am seeing dropped packets. The PPS rate is only about 30k which should not be that much Oct 8 02:15:02 c1 kernel: em2: Excessive collisions = 0 Oct 8 02:15:02 c1 kernel: em2: Sequence errors = 0 Oct 8 02:15:02 c1 kernel: em2: Defer count = 0 Oct 8 02:15:02 c1 kernel: em2: Missed Packets = 2068 Oct 8 02:15:02 c1 kernel: em2: Receive No Buffers = 280 Oct 8 02:15:02 c1 kernel: em2: Receive Length Errors = 0 Oct 8 02:15:02 c1 kernel: em2: Receive errors = 3 Oct 8 02:15:02 c1 kernel: em2: Crc errors = 3 Oct 8 02:15:02 c1 kernel: em2: Alignment errors = 0 Oct 8 02:15:02 c1 kernel: em2: Collision/Carrier extension errors = 0 Oct 8 02:15:02 c1 kernel: em2: RX overruns = 17 Oct 8 02:15:02 c1 kernel: em2: watchdog timeouts = 0 Oct 8 02:15:02 c1 kernel: em2: XON Rcvd = 0 Oct 8 02:15:02 c1 kernel: em2: XON Xmtd = 0 Oct 8 02:15:02 c1 kernel: em2: XOFF Rcvd = 0 Oct 8 02:15:02 c1 kernel: em2: XOFF Xmtd = 0 Oct 8 02:15:02 c1 kernel: em2: Good Packets Rcvd = 146043044 Oct 8 02:15:02 c1 kernel: em2: Good Packets Xmtd = 75481090 Oct 8 02:15:02 c1 kernel: em2: TSO Contexts Xmtd = 0 Oct 8 02:15:02 c1 kernel: em2: TSO Contexts Failed = 0 % vmstat -i interrupt total rate irq1: atkbd0 5 0 irq4: sio0 10094 0 irq16: em0 291014020 5831 irq17: em1 em2 em3 298574806 5983 irq19: atapci1 53969 1 cpu0: timer 99802510 1999 cpu1: timer 99791176 1999 Total 789246580 15815 Load avg is quite low, although top doesnt show any interrupt activity for some reason. The settings are all default % sysctl -a dev.em.2 dev.em.2.%desc: Intel(R) PRO/1000 Network Connection Version - 6.6.6 dev.em.2.%driver: em dev.em.2.%location: slot=0 function=0 dev.em.2.%pnpinfo: vendor=0x8086 device=0x108c subvendor=0x8086 subdevice=0x348f class=0x02 dev.em.2.%parent: pci3 dev.em.2.debug_info: -1 dev.em.2.stats: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 em0: Intel(R) PRO/1000 Network Connection Version - 6.6.6 port 0x3020-0x303f mem 0x8826-0x8827,0x8824-0x8825 irq 16 at device 0.0 on pci2 em0: Ethernet address: 00:15:17:0b:70:98 em0: [FAST] em1: Intel(R) PRO/1000 Network Connection Version - 6.6.6 port 0x3000-0x301f mem 0x8822-0x8823,0x8820-0x8821 irq 17 at device 0.1 on pci2 em1: Ethernet address: 00:15:17:0b:70:99 em1: [FAST] pcib3: ACPI PCI-PCI bridge at device 28.5 on pci0 pci3: ACPI PCI bus on pcib3 em2: Intel(R) PRO/1000 Network Connection Version - 6.6.6 port 0x2000-0x201f mem 0x8818-0x8819,0x8810-0x8817 irq 17 at device 0.0 on pci3 em2: Ethernet address: 00:15:17:1e:94:0b em2: [FAST] pci3: simple comms, UART at device 0.3 (no driver attached) pci3: serial bus at device 0.4 (no driver attached) pcib4: ACPI PCI-PCI bridge at device 30.0 on pci0 pci4: ACPI PCI bus on pcib4 pci4: display, VGA at device 4.0 (no driver attached) em3: Intel(R) PRO/1000 Network Connection Version - 6.6.6 port 0x1100-0x113f mem 0x8802-0x8803,0x8800-0x8801 irq 17 at device 5.0 on pci4 em3: Ethernet address: 00:15:17:1e:94:0c em3: [FAST] [EMAIL PROTECTED]:0:0: class=0x02 card=0x115e8086 chip=0x105e8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/1000 PT' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint [EMAIL PROTECTED]:0:1: class=0x02 card=0x115e8086 chip=0x105e8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/1000 PT' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint [EMAIL PROTECTED]:0:0: class=0x02 card=0x348f8086 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/1000 PM' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint [EMAIL PROTECTED]:5:0: class=0x02 card=0x348f8086 chip=0x10768086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device =
Re: Heads UP - MFC for em coming shortly
On 10/8/07, Mike Tancsa [EMAIL PROTECTED] wrote: At 04:28 PM 10/5/2007, Jack Vogel wrote: I am preparing to update the em driver to the equivalent of my 6.6.6 driver. Just doing some last minute sanity checking, I hope to the checkin before end of day. Hi, thanks for fixing the compile issue, but I have another possible problem. Do you know if there were any performance regressions with this rev? On one firewall / router, I am seeing dropped packets. The PPS rate is only about 30k which should not be that much So the missed packets are only showing up on em2? Uh, and that is a management-capable 82573, one that is often a problem without the eeprom patched, did you do that sometime in the past, I don't remember who did and who didnt :) Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
At 04:36 PM 10/8/2007, Jack Vogel wrote: So the missed packets are only showing up on em2? Hi, Yes, but thats where all the packets come in. Uh, and that is a management-capable 82573, one that is often a problem without the eeprom patched, did you do that sometime in the past, I don't remember who did and who didnt :) No, I havent. Where do I find this program and how can I find out if I need it or not. The box in question is about 100miles away and it would be handy to confirm its needed remotely ---Mik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
On 10/8/07, Mike Tancsa [EMAIL PROTECTED] wrote: At 04:36 PM 10/8/2007, Jack Vogel wrote: So the missed packets are only showing up on em2? Hi, Yes, but thats where all the packets come in. Uh, and that is a management-capable 82573, one that is often a problem without the eeprom patched, did you do that sometime in the past, I don't remember who did and who didnt :) No, I havent. Where do I find this program and how can I find out if I need it or not. The box in question is about 100miles away and it would be handy to confirm its needed remotely Search thru the archives of this mailing list, look for 82573. There is a DOS patcher that I have sent out a couple times. Its harmless to run it, if the adapter is wrong or it doesnt need the patch it should tell you. What it does it change a bit in the EEPROM programming of the MANC register. If you can't find it in the archives let me know and I'll send it to you. Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
At 08:36 PM 10/8/2007, Jack Vogel wrote: Search thru the archives of this mailing list, look for 82573. There is a DOS patcher that I have sent out a couple times. Its harmless to run it, if the adapter is wrong or it doesnt need the patch it should tell you. What it does it change a bit in the EEPROM programming of the MANC register. If you can't find it in the archives let me know and I'll send it to you. Thanks, I did find this reference http://www.higherorder.com.au/2007/6/25/intel_82573_patch Is there a way from FreeBSD to tell remotely if its needed ? ---Mike Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
On 10/8/07, Mike Tancsa [EMAIL PROTECTED] wrote: At 08:36 PM 10/8/2007, Jack Vogel wrote: Search thru the archives of this mailing list, look for 82573. There is a DOS patcher that I have sent out a couple times. Its harmless to run it, if the adapter is wrong or it doesnt need the patch it should tell you. What it does it change a bit in the EEPROM programming of the MANC register. If you can't find it in the archives let me know and I'll send it to you. Thanks, I did find this reference http://www.higherorder.com.au/2007/6/25/intel_82573_patch Is there a way from FreeBSD to tell remotely if its needed ? Well, there would be a way, reading the MANC register and seeing if the suspect bit is present, but am not sure if there is some important point at which the thing gets misprogrammed, its just best to use the patcher, its harmless if its not needed. Sorry, I realize its a hassle to boot to that wonder DOS :) Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
On Sat, Oct 06, 2007 at 11:18:58PM +0100, Bartosz Fabianowski wrote: /home/obj/src/sys/dev/em/if_em.c: In function `em_allocate_intr': /home/obj/src/sys/dev/em/if_em.c:2647: warning: passing arg 6 of `bus_setup_intr' from incompatible pointer type /home/obj/src/sys/dev/em/if_em.c:2647: error: too many arguments to function `bus_setup_intr' This has just been fixed, but for me it now breaks with: /usr/src/sys/modules/em/../../dev/em/if_em.c: In function `em_init_locked': /usr/src/sys/modules/em/../../dev/em/if_em.c:1299: error: structure has no member named `laa_is_present' /usr/src/sys/modules/em/../../dev/em/if_em.c: In function `em_local_timer': /usr/src/sys/modules/em/../../dev/em/if_em.c:2400: error: structure has no member named `mac_type' /usr/src/sys/modules/em/../../dev/em/if_em.c:2401: error: structure has no member named `laa_is_present' The same thing here. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
On Sat, Oct 06, 2007 at 11:18:58PM +0100, Bartosz Fabianowski wrote: This has just been fixed, but for me it now breaks with: /usr/src/sys/modules/em/../../dev/em/if_em.c: In function `em_init_locked': /usr/src/sys/modules/em/../../dev/em/if_em.c:1299: error: structure has no member named `laa_is_present' /usr/src/sys/modules/em/../../dev/em/if_em.c: In function `em_local_timer': /usr/src/sys/modules/em/../../dev/em/if_em.c:2400: error: structure has no member named `mac_type' /usr/src/sys/modules/em/../../dev/em/if_em.c:2401: error: structure has no member named `laa_is_present' The log for latest commit says: Couple corrections on the MFC, first POLLING had a 7.0 interface left in, thanks to those that caught this. That's fixed indeed, thanks to Jack Vogel. Second, there was a 82571 fix in the last delta that got missed, it has now been converted and added. That part was obviously not compile-tested and is broken. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
On Fri, Oct 05, 2007 at 01:28:20PM -0700, Jack Vogel wrote: I am preparing to update the em driver to the equivalent of my 6.6.6 driver. Just doing some last minute sanity checking, I hope to the checkin before end of day. Latest fix works for me (c) :-) Thank you, Jack, for your patience and cooperation. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
On Fri, Oct 05, 2007 at 01:28:20PM -0700, Jack Vogel wrote: I am preparing to update the em driver to the equivalent of my 6.6.6 driver. Just doing some last minute sanity checking, I hope to the checkin before end of day. The MFC broke compilation of kernel containing both device em and options DEVICE_POLLING: /home/obj/src/sys/dev/em/if_em.c: In function `em_allocate_intr': /home/obj/src/sys/dev/em/if_em.c:2647: warning: passing arg 6 of `bus_setup_intr' from incompatible pointer type /home/obj/src/sys/dev/em/if_em.c:2647: error: too many arguments to function `bus_setup_intr' Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
On 10/6/07, Eugene Grosbein [EMAIL PROTECTED] wrote: On Fri, Oct 05, 2007 at 01:28:20PM -0700, Jack Vogel wrote: I am preparing to update the em driver to the equivalent of my 6.6.6 driver. Just doing some last minute sanity checking, I hope to the checkin before end of day. The MFC broke compilation of kernel containing both device em and options DEVICE_POLLING: /home/obj/src/sys/dev/em/if_em.c: In function `em_allocate_intr': /home/obj/src/sys/dev/em/if_em.c:2647: warning: passing arg 6 of `bus_setup_intr' from incompatible pointer type /home/obj/src/sys/dev/em/if_em.c:2647: error: too many arguments to function `bus_setup_intr' Eugene Grosbein I don't think it was in HEAD to be MFCed? -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
On Sat, Oct 06, 2007 at 10:08:39PM +0300, Abdullah Ibn Hamad Al-Marri wrote: On 10/6/07, Eugene Grosbein [EMAIL PROTECTED] wrote: On Fri, Oct 05, 2007 at 01:28:20PM -0700, Jack Vogel wrote: I am preparing to update the em driver to the equivalent of my 6.6.6 driver. Just doing some last minute sanity checking, I hope to the checkin before end of day. The MFC broke compilation of kernel containing both device em and options DEVICE_POLLING: /home/obj/src/sys/dev/em/if_em.c: In function `em_allocate_intr': /home/obj/src/sys/dev/em/if_em.c:2647: warning: passing arg 6 of `bus_setup_intr' from incompatible pointer type /home/obj/src/sys/dev/em/if_em.c:2647: error: too many arguments to function `bus_setup_intr' Eugene Grosbein I don't think it was in HEAD to be MFCed? Correct. That code has not yet been added to -CURRENT, so technically it was not an MFC (Merge From -Current), but rather an MFV (Merge From Vendor). -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
/home/obj/src/sys/dev/em/if_em.c: In function `em_allocate_intr': /home/obj/src/sys/dev/em/if_em.c:2647: warning: passing arg 6 of `bus_setup_intr' from incompatible pointer type /home/obj/src/sys/dev/em/if_em.c:2647: error: too many arguments to function `bus_setup_intr' This has just been fixed, but for me it now breaks with: /usr/src/sys/modules/em/../../dev/em/if_em.c: In function `em_init_locked': /usr/src/sys/modules/em/../../dev/em/if_em.c:1299: error: structure has no member named `laa_is_present' /usr/src/sys/modules/em/../../dev/em/if_em.c: In function `em_local_timer': /usr/src/sys/modules/em/../../dev/em/if_em.c:2400: error: structure has no member named `mac_type' /usr/src/sys/modules/em/../../dev/em/if_em.c:2401: error: structure has no member named `laa_is_present' - Bartosz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Heads UP - MFC for em coming shortly
I am preparing to update the em driver to the equivalent of my 6.6.6 driver. Just doing some last minute sanity checking, I hope to the checkin before end of day. This will provide support for devices up to our latest, the next stage I'm planning will incorporate multiqueue and multiple locks that are already in my Oplin driver (ixgbe) but this will take a bit longer. This driver has the support for TSO in it but its not on by default, as soon as Andre is able to get that MFC'd it can be enabled via a compile option. Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Heads UP - MFC for em coming shortly
Jack Vogel wrote: I am preparing to update the em driver to the equivalent of my 6.6.6 driver. Just doing some last minute sanity checking, I hope to the checkin before end of day. This will provide support for devices up to our latest, the next stage I'm planning will incorporate multiqueue and multiple locks that are already in my Oplin driver (ixgbe) but this will take a bit longer. This driver has the support for TSO in it but its not on by default, as soon as Andre is able to get that MFC'd it can be enabled via a compile option. Hello, Jack! Remember, i wrote about problems with TSO (dropping send perfomace). I just posted news about it. Switching to SCHED_ULE solved to problem or.. i could be switching from HZ 1000 to HZ 100. I need to check into it. I hope it helps in some way. -- Regards, Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
