Hi,
On Fri, 23 Sep 2005, Thomas Gleixner wrote:
> The idea of ktimers is to use the requested time given by a timespec in
> human time without any corrections, so we actually can avoid the above.
>
> Also doing time ordered insertion into a list introduces incompabilities
> between 32/64 bit storage formats.
Except that the (time) range of the list would be limited I don't really
see a big difference.
Anyway, the biggest cost is the conversion from/to the 64bit ns value and
if its main use is sorting, you can use something like this:
typedef union {
u64 tv64;
struct {
#ifdef __BIG_ENDIAN
u32 sec, nsec;
#else
u32 nsec, sec;
#endif
} tv;
} ktimespec;
To compare two time values the tv64 value is sufficient.
bye, Roman
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|