Re: [PATCH] Win32 equivalent to GetTickCount systemcall (i386)

Andi Kleen a écrit :

"David Engraf" <[email protected]> writes:

times has only 10ms resolution, we need at least 1ms.

It actually has jiffies resultion. Your measurements must have been
quite off.

I beg to differ: times has a 10 ms resolution ( ie 1/USER_HZ)

times() is supposed to return clock_t expressed in USER_HZ, wich is still 100, regardless of the kernel HZ

I just checked sources and sys_times() do use jiffies_64_to_clock_t()

Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] Win32 equivalent to GetTickCount systemcall (i386)
    • From: Andi Kleen <[email protected]>

• References:
  • Re: [PATCH] Win32 equivalent to GetTickCount systemcall (i386)
    • From: Bernd Petrovitsch <[email protected]>
  • Re: [PATCH] Win32 equivalent to GetTickCount systemcall (i386)
    • From: "David Engraf" <[email protected]>
  • Re: [PATCH] Win32 equivalent to GetTickCount systemcall (i386)
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: copy_from_user/copy_to_user question
• Next by Date: Re: RFC: Starting a stable kernel series off the 2.6 kernel
• Previous by thread: Re: [PATCH] Win32 equivalent to GetTickCount systemcall (i386)
• Next by thread: Re: [PATCH] Win32 equivalent to GetTickCount systemcall (i386)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]