At 06:06 PM 11/30/2006, Hubert Feyrer wrote:

>[adding tech-net@ as I don't really know what to answer...
>
>  Context: adding NetBSD in the benchmark at
>  http://www.tancsa.com/blast.html, with the wm(4) driver in
>  -current, as it's not available in 3.1]
>
>
>On Thu, 30 Nov 2006, Mike Tancsa wrote:
>>Gave it a try and I posted the results on the web page.  The Intel 
>>driver doesnt seem to work too well.  Is there debugging in this kernel ?
>
>That sounds indeed not so bright. I do not know about the wm(4) 
>driver, but maybe someone on tech-net@ (CC:d) has an idea. IIRC 
>that's with a -current (HEAD) GENERIC kernel and the wm(4) driver, 
>while bge(4) driver works ok.
>
>What I wonder is: how does the bge(4) driver perform under -current, 
>do you have numbers for that? (Just to make sure it's not -curren that's hosed)

Done and posted.  I also looked at netstat -q and indeed it reports 
dropped packets

# netstat -q
arpintrq:
         queue length: 0
         maximum queue length: 50
         packets dropped: 151
ipintrq:
         queue length: 0
         maximum queue length: 256
         packets dropped: 133721212
ip6intrq:
         queue length: 0
         maximum queue length: 256
         packets dropped: 0
atintrq1:
         queue length: 0
         maximum queue length: 256
         packets dropped: 0
atintrq2:
         queue length: 0
         maximum queue length: 256
         packets dropped: 0
clnlintrq:
         queue length: 0
         maximum queue length: 256
         packets dropped: 0
ppoediscinq:
         queue length: 0
         maximum queue length: 256
         packets dropped: 0
ppoeinq:
         queue length: 0
         maximum queue length: 256
         packets dropped: 0