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:22 PM, M. Koehrer <mathias_koehrer@xxxxxxxx> wrote:
> Does it help to run the posix threads with realtime priority by calling
> pthread_setschedparam() with SCHED_FIFO and a suitable priority?
> As fas as I understand your code, the threads run with standard (non realtime
> priority).

Yes. I tried this with a chrt -f 99. But I still end up getting those
large deviations.

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 ?

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