linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "M. Koehrer" <mathias_koehrer@arcor.de>
To: pradysam@gmail.com, linux-rt-users@vger.kernel.org
Cc: rachana.rao@in.abb.com
Subject: Re: mq_timedrecieve timeout accuracy
Date: Wed, 24 Mar 2010 14:22:14 +0100 (CET)	[thread overview]
Message-ID: <8226231.1269436934345.JavaMail.ngmail@webmail10.arcor-online.net> (raw)
In-Reply-To: <6d09081c1003240527r471ee34etbba11b4b7c7e92b3@mail.gmail.com>

> We are dealing with an application that is a fairly heavy user of
> POSIX message queues. While running this application I seemed to have
> stumbled upon the fact that the timeout in the mq_timedrecieve is
> innaccurate to the tune of a more than 5-6 miliseconds and that it is
> fairly consistent even at its highest priority.
> 
> Cyclictest on the same machine gives me a max deviation of about 7uS,
> so I guess my timers (hrt) are functioning alright.
> 
> Here is a small program I hacked up from the LTP sources to
> demonstrate this behaviour (attached). I ran this on a dual core
> 2.5Ghz cpu and a uniprocessor 1.5Ghz cpu (cpuinfo below). On the
> dual-core I can see that its off by 1-2 miliseconds but on the 1.5 Ghz
> celeron its off by 6-8 miliseconds sometimes.
> 
> kernel version: 2.6.33.1-rt10
> 
> Usage: ./send_rev_2 <timeout_in_miliseconds>
> 
> $ cat /proc/cpuinfo
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 13
> model name      : Intel(R) Celeron(R) M processor         1.50GHz
> stepping        : 8
> cpu MHz         : 1500.111
> cache size      : 1024 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 2
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov
> clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up bts
> 
> Also attaached is my .config.
> 
> thanks in advance
> regards
> /prady
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).


Mathias



-- 
Mathias Koehrer
mathias_koehrer@arcor.de


Holt sich Schumi den 8. Titel seiner Formel-1-Karriere? Schumi reloaded, alle Infos, Fahrer- und Team-Portraits und das Formel-1-Experten-Quiz finden Sie hier: http://www.arcor.de/rd/footer.f1

  parent reply	other threads:[~2010-03-24 13:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 12:27 mq_timedrecieve timeout accuracy Pradyumna Sampath
2010-03-24 13:12 ` John Kacur
2010-03-24 13:21 ` Sujit K M
2010-03-24 13:22 ` M. Koehrer [this message]
2010-03-24 13:37   ` Pradyumna Sampath
2010-03-24 13:45     ` Sujit K M
2010-03-24 13:47       ` Pradyumna Sampath
2010-03-24 14:03     ` Pradyumna Sampath
2010-03-24 15:46       ` [PATCH] " Pradyumna Sampath
2010-03-29 15:08         ` [PATCH] " Carsten Emde
2010-03-30  7:41           ` Pradyumna Sampath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8226231.1269436934345.JavaMail.ngmail@webmail10.arcor-online.net \
    --to=mathias_koehrer@arcor.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=pradysam@gmail.com \
    --cc=rachana.rao@in.abb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).