From: Neil T. Dantam <ntd@gatech.edu>
To: xenomai@xenomai.org
Subject: [Xenomai] Slow Sockets and Pipes with POSIX Skin
Date: Mon, 21 Oct 2013 17:41:00 -0400 [thread overview]
Message-ID: <l44714$imt$1@ger.gmane.org> (raw)
I am seeing some surprisingly high latencies for socket and pipe
communication using Xenomai's POSIX skin. Pipes, localhost TCP/UDP,
and local domain sockets all show worst case latency of ~100us on
Xenomai 2.6.2.1/Linux 3.4.6 on a Xeon E3-1270v2. Average and 99%
latency is under 20us. Running `xeno-test latency` gives worst-case
latency of ~10us. POSIX message queues have worst case latency below
20us.
I've done the following to reduce latency:
* Disabled CPU frequency scaling
* Disabled USB
* Set real-time scheduling priority
* Prefaulted the stack
The 100us delay seems like what one get from a System Management
Interrupt (SMI). However, since `xeno-test latency` and message
queues both show low latency, it seems unlikely that this could be the
issue.
Has anyone else encountered (or not encountered) similar performance
issues with pipes and sockets?
Cheers,
-ntd
next reply other threads:[~2013-10-21 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 21:41 Neil T. Dantam [this message]
2013-10-21 21:49 ` [Xenomai] Slow Sockets and Pipes with POSIX Skin Gilles Chanteperdrix
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='l44714$imt$1@ger.gmane.org' \
--to=ntd@gatech.edu \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.