john stultz wrote: > How about using getnstimeofday() only if the kernel clocksource is tsc? > Presumably anyone running into this problem would have modern high > performance hardware with working tsc. This might be difficult, as clocksources can change while the system is running. Further, any checks for specific clocksources would be very architecture specific. A fast-timekeeping flag could be used, but would be a fairly subjective metric (ie: would there be issues if the fast clock on a slower system is slower then a slow clock on a fast system, etc). That's partly why I suggested a mount option. It just would be nice if the kernel could "do the right thing" without the user having to set some option or sysctl. The problem is infrequently seen, difficult to diagnose, and not obvious as to whether it's a client or server issue. I don't think your typical user, or even your typical professional sysadmin, is going to get this right if it requires a setting. Having said that, it's not obvious to me how to do this automatically. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
