From: kuznet@ms2.inr.ac.ru Date: Thu, 17 Jan 2002 22:00:52 +0300 (MSK) Hmm, am I not alone holding an 386 on my desk? :-) I am afraid it is the only machine in readius of kilometer here where get_fast_time != do_gettimeofday identically. But the issue is right if to be pedantic, on 386 get_fast_time() is really badly broken. And an option returning it to do_gettimeofday() really could exist. Especially tking into account that this is incredibly easy. Actually, if one greps the tree for get_fast_time() usage, it is all totally bogus. Outside of this one packet timestamping place, the only other places using get_fast_time() are in things like knfsd startup etc. (ie. totally non-critical places). Really, I would suggest that we just kill off get_fast_time() entirely and just use do_gettimeofday() everywhere. It's like a 10 minute hack. - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html