From: Pavel Machek <pavel@suse.cz>
To: Geir Thomassen <geirt@powertech.no>, linux-kernel@vger.kernel.org
Cc: tytso@mit.edu
Subject: Re: Serial port latency
Date: Fri, 23 Mar 2001 00:25:16 +0100 [thread overview]
Message-ID: <20010323002516.B126@bug.ucw.cz> (raw)
In-Reply-To: <3ABA42A8.A806D0E7@powertech.no>
In-Reply-To: <3ABA42A8.A806D0E7@powertech.no>; from Geir Thomassen on Thu, Mar 22, 2001 at 07:21:28PM +0100
Hi!
> My program controls a device (a programmer for microcontrollers) via the
> serial port. The program sits in a tight loop, writing a few (typical 6)
> bytes to the port, and waits for a few (typ. two) bytes to be returned from
> the programmer.
>
> The program works, but it is very slow. I use an oscilloscope to monitor the
> serial lines, and notices that there is a large delay between the returned
> data, and the next new command. I really don't know if the delay is on the
> sending or the receiving side (or both).
>
> This is what the program does:
>
> fd=open("/dev/ttyS0",O_NOCTTY | O_RDWR);
>
> tcsetattr(fd,TCSANOW, &tio); /* setting baud, parity, raw mode, etc */
>
> while() {
> write( 6 bytes); /* send command */
> read( 2 bytes); /* wait for reply */
> }
>
>
> The device on the serial port responds in typ. 10 ms, but the software uses
> over 500ms to get the reply and send the next command. Why is this happening ?
> I have a feeling that there is something obvious I am missing (like line
> buffering, but that's a stdio (libc) thing, isn't it ?).
Set HZ=1000 in include/asm/params.h and see if it helps.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
next prev parent reply other threads:[~2001-03-23 11:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 18:21 Serial port latency Geir Thomassen
2001-03-22 20:08 ` Theodore Tso
2001-03-22 20:32 ` Geir Thomassen
2001-03-22 20:55 ` Paul Fulghum
2001-03-22 22:44 ` Theodore Tso
[not found] ` <20010322141937.C22479@universal-fasteners.com>
2001-03-22 21:02 ` Geir Thomassen
2001-03-22 21:52 ` Jonathan Lundell
2001-03-22 23:25 ` Pavel Machek [this message]
2001-03-23 14:43 ` Geir Thomassen
[not found] <Pine.LNX.4.20.0103221219410.3343-100000@linuxtaj.korpivaara.org>
2001-03-22 20:03 ` Geir Thomassen
2001-03-22 20:17 ` Trent Jarvi
-- strict thread matches above, loose matches on Subject: below --
2001-03-22 21:45 Manfred Spraul
[not found] <000401c0b319517fea9@local>
2001-03-25 23:10 ` Pavel Machek
2001-03-29 7:58 ` Manfred Spraul
2001-03-30 22:36 ` Pavel Machek
2001-03-31 22:09 ` Manfred Spraul
2001-04-10 0:37 ` Andrea Arcangeli
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=20010323002516.B126@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=geirt@powertech.no \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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