gettimeofday resolution seriously degraded in test9
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Stephen Hemminger
Stephen> This should work better. Patch against 2.6.0-test9
Why not use the time-interpolator interface defined in timex.h? It should handle such things without any special hacks.
--david
Quoted 8 lines · On 28 Oct 2003 11:19:21 -0800 David Mosberger-Tang <[email protected]>…
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Stephen Hemminger
Stephen> This should work better. Patch against 2.6.0-test9
Why not use the time-interpolator interface defined in
timex.h? It should handle such things without any special hacks.--david
Because it has not been used yet outside of ia64. It would be worth investigating post 2.6.0 if it could be shown to be as fast and more correct. Several people have talked about redoing the existing mess, but now is not the time to attack this dragon...
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Stephen Hemminger
Stephen> On 28 Oct 2003 11:19:21 -0800
Quoted 1 line · Stephen> David Mosberger-Tang <[email protected]> wrote:
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Stephen Hemminger
Stephen> This should work better. Patch against 2.6.0-test9
Quoted 2 lines
Quoted 2 lines
Why not use the time-interpolator interface defined in
timex.h? It should handle such things without any special hacks.
Stephen> Because it has not been used yet outside of ia64. It would Stephen> be worth investigating post 2.6.0 if it could be shown to Stephen> be as fast and more correct. Several people have talked Stephen> about redoing the existing mess, but now is not the time to Stephen> attack this dragon...
OK, I certainly agree that it's not something that should be done in a rush, so it's definitely post 2.6.0.
--david
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [RFC] possible erronous use of tick_usec in do_gettimeofday
Quoted 5 lines · Joe Korty
test10's version of
do_gettimeofdayis usingtick_usecwhich is defined in terms ofUSER_HZnot HZ.Against 2.6.0-test10-bk1. Compiled, not tested, for comment only.
I added the changes to x86-64, but at least ping still complains that the time is going backwards. The machine is running ntpd and has a high drift (AMD 8111 chipset, doesn't have the most stable timer in the world)
-Andi