Messages in this thread | | | Date | Tue, 11 Mar 2003 14:44:48 -0800 | From | Andrew Morton <> | Subject | Re: Runaway cron task on 2.5.63/4 bk? |
| |
george anzinger <george@mvista.com> wrote: > > Ok, here is what I have. I changed nano sleep to use a local 64-bit > value for the target expire time in jiffies. As much as MAX-INT/2-1 > will be put in the timer at any one time. It loops till the target > time is met or exceeded. The changes affect (clock)nanosleep only and > not timers (they still error out for large values). > > Issues: The conversion of timespec to jiffies_64 is most easily done > by the asm mpy instruction, which results in the required 64 bit > result, but C doesn't want to do this sort of thing.
gcc will generate 64bit * 64bit multiplies without resorting to any library code and you can probably do the division with do_div().
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |