After a conference call today, it was decided that a merge of my Intel driver base and the STABLE code would take place. This code undoes the INTR_FAST/taskqueue approach for right now. Work will continue to get that to work, but the hope is that this driver will be more stable for the 6.2 release. I encourage everyone that has been having issues to pull the new driver and give us feedback. A few select testers so far have seen stable performance. Cheers, Jack
On Friday, 27 October 2006 at 18:44:37 -0700, Jack Vogel wrote:> After a conference call today, it was decided that a merge of > my Intel driver base and the STABLE code would take place. > > This code undoes the INTR_FAST/taskqueue approach for right > now. Work will continue to get that to work, but the hope is that > this driver will be more stable for the 6.2 release. > > I encourage everyone that has been having issues to pull the > new driver and give us feedback. A few select testers so far > have seen stable performance. > > Cheers, > > Jack > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"Hi, Jack. Could you please post here exact revision number of this merge, just for history. -- ====================================================================== - Best regards, Nikolay Pavlov. <<<----------------------------------- ======================================================================
On 10/28/06, Nikolay Pavlov <quetzal@zone3000.net> wrote:> On Friday, 27 October 2006 at 18:44:37 -0700, Jack Vogel wrote: > > After a conference call today, it was decided that a merge of > > my Intel driver base and the STABLE code would take place. > > > > This code undoes the INTR_FAST/taskqueue approach for right > > now. Work will continue to get that to work, but the hope is that > > this driver will be more stable for the 6.2 release. > > > > I encourage everyone that has been having issues to pull the > > new driver and give us feedback. A few select testers so far > > have seen stable performance. > > > > Cheers, > > > > Jack > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > Hi, Jack. > Could you please post here exact revision number of this merge, just for > history.Sure thing: Log: Merge of Intel 6.2.9 em driver code. Approved by: re, scottl, jhb, pdeuskar Revision Changes Path 1.65.2.19 +731 -589 src/sys/dev/em/if_em.c 1.32.2.5 +97 -71 src/sys/dev/em/if_em.h 1.16.2.4 +574 -531 src/sys/dev/em/if_em_hw.c 1.15.2.5 +96 -148 src/sys/dev/em/if_em_hw.h 1.14.2.3 +46 -52 src/sys/dev/em/if_em_osdep.h
On Sat, 28 Oct 2006 03:44:37 +0200, Jack Vogel <jfvogel@gmail.com> wrote:> After a conference call today, it was decided that a merge of > my Intel driver base and the STABLE code would take place. > > This code undoes the INTR_FAST/taskqueue approach for right > now. Work will continue to get that to work, but the hope is that > this driver will be more stable for the 6.2 release. > > I encourage everyone that has been having issues to pull the > new driver and give us feedback. A few select testers so far > have seen stable performance.I'm running this at my workstation at work. Today it still had DEVICE_POLLING compiled in, but no +polling on the interface. It looks ok. I recompiled without DEVICE_POLLING in the kernel tonight and wil report when I have more experience tomorrow. I didn't really stress-test it, but that wasn't necessary in the past to trigger the watchdog timeouts. A little CPU load did the job in the past. Ronald. -- Ronald Klop Amsterdam, The Netherlands
On Wed, 01 Nov 2006 00:48:46 +0100, Ronald Klop <ronald-freebsd8@klop.yi.org> wrote:> On Sat, 28 Oct 2006 03:44:37 +0200, Jack Vogel <jfvogel@gmail.com> wrote: > >> After a conference call today, it was decided that a merge of >> my Intel driver base and the STABLE code would take place. >> >> This code undoes the INTR_FAST/taskqueue approach for right >> now. Work will continue to get that to work, but the hope is that >> this driver will be more stable for the 6.2 release. >> >> I encourage everyone that has been having issues to pull the >> new driver and give us feedback. A few select testers so far >> have seen stable performance. > > I'm running this at my workstation at work. Today it still had > DEVICE_POLLING compiled in, but no +polling on the interface. It looks > ok. I recompiled without DEVICE_POLLING in the kernel tonight and wil > report when I have more experience tomorrow. > I didn't really stress-test it, but that wasn't necessary in the past to > trigger the watchdog timeouts. A little CPU load did the job in the past. > > Ronald.Without DEVICE_POLLING in the kernel my em0 also survived the day. But again I didn't stresstest it, because there was no time to do that at work. Ronald. -- Ronald Klop Amsterdam, The Netherlands