On Thu, Mar 21, 2002 at 05:41:51PM -0600, Grant Edwards wrote: > > > A few months back, I upgraded from RH6.2 (2.2.x) to RH7.2 > > (2.4.10). My timestamps used to have 1us resolution, now they > > have 10ms resolution. This really sucks, since I'm trying to > > measure thing to an accuracy of 200us or so. > [...] > > One would guess there's something wrong with network stack > > configuration in RH7.2, but I don't know where to look. > > Sorry for the bother. It indeed appears to be something RedHat > did to the kenel. I compiled 2.4.18 fresh from kernel.org, and > it works fine now.
What happens with 2.4.10 fresh from kernel.org? If it has the same problem, perhaps it's some bug fixed between 2.4.10 and 2.4.18. If I remember correctly, there might be, in at least some versions of the kernel, some configuration flag you have to turn on to get time stamps of various sorts to use high-resolution timers. Does anybody know what they are? That would be useful to put into the tcpdump FAQ. - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
