In article <[EMAIL PROTECTED]>, Poul-Henning Kamp <[EMAIL PROTECTED]> wrote: > In message <[EMAIL PROTECTED]>, John Polstra writes: > Could you try this combination: > > NTIMECOUNTER = HZ (or even 5 * HZ) > tco_method = 0 > no splhigh protection for microuptime() ?
After 25 minutes testing that with NTIMECOUNTER=50000, I haven't gotten any microuptime messages. So it appears that my problem was just that the current timecounter wrapped all the way around the ring while microuptime was interrupted, due to the high HZ value and the heavy interrupt load. I'm sorry I didn't try this sooner, when you suggested it. After lunch I'll try NTIMECOUNTER=HZ (10000 in my case). That sounds like a nice default value to me. It would be interesting to see whether this same fix also works in -current. I'm not sure yet if I can test that here or not. I haven't tried building my netgraph module under -current yet. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
