Re: mq_timedrecieve timeout accuracy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, Mar 24, 2010 at 2:37 PM, Pradyumna Sampath <pradysam@xxxxxxxxx> wrote:
> John, mq_timedrecieve takes abstime. Isnt it supposed to be
> CLOCK_REALTIME ? Anyway, I tried with MONOTONIC .. mq_timedrecieve
> doesnt block on that.
>
> I was just looking at some code in the kernel. linux/ipc/mqueue.c
> +442. This line says:
>
> time = schedule_timeout(timeout);
>
> Maybe this is why produces a timeout that is inaccurate. Shouldnt it
> be schedule_hrtimeout ?

Ok, I just moved the HZ value from 250 to 1000 and the accuracy has
improved significantly from 5-7 to 1-2 miliseconds. But IMHO, we
should still change schedule_timeout to schedule_hrtimeout for better
accuracy on the timeout because in many cases 1-2 miliseconds is just
not good enough.

I will try to push out a patch for this later today.

regards
/prady

-- 
http://www.prady.in
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux