From: Steven Vacca <svacca@valcom.com>
To: "LinuxEmbeddedMailList (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Thruput slow unless select() on stdin frequently
Date: Mon, 4 Nov 2002 15:13:41 -0500 [thread overview]
Message-ID: <01C28414.C30A9C20.svacca@valcom.com> (raw)
--- stdin appears to block until a select() tests it, thus slowing
system code execution way down. ---
My MPC860T app executes UDP recvfrom()'s and sendto()'s
at regular intervals. The recvfrom() UDP pkt data is queued with
a buffer descriptor for transmission on a QMC channel to an
external device. The data read from the device on a QMC
channel is queued with a buffer descriptor for subsequent sendto().
But if I do not constantly execute a select() (timeout = 10us)
on stdin (serial keyboard - not being used often) at a fast enough
rate (i.e. if the select() is executed in it's own thread and doesn't
get scheduled frequently enough) the code execution slows way
down, and I find that the queued QMC channel data, residing
in the circular queues doesn't get transmitted fast enough
and the queues grow and grow. Doing no select() on stdin
basically shuts the QMC buff desc processing down.
It's as though, even with no serial chars coming in, stdin
blocks until the select() tests it. I need to avoid this blocking, yet
still periodically check for a serial key input on stdin.
Any ideas out there in Linux Embedded-land?
Thanks,
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-11-04 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 20:13 Steven Vacca [this message]
2002-11-05 9:00 ` Thruput slow unless select() on stdin frequently Georg Klug
-- strict thread matches above, loose matches on Subject: below --
2002-11-06 13:15 Steven Vacca
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=01C28414.C30A9C20.svacca@valcom.com \
--to=svacca@valcom.com \
--cc=linuxppc-embedded@lists.linuxppc.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 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).