From: Paul Fulghum <paulkf@microgate.com>
To: Raphael Hertzog <hertzog@debian.org>
Cc: Lee Revell <rlrevell@joe-job.com>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: How to avoid serial port buffer overruns?
Date: Thu, 17 Aug 2006 11:40:47 -0500 [thread overview]
Message-ID: <44E49C0F.7030600@microgate.com> (raw)
In-Reply-To: <20060817161042.GC10818@ouaza.com>
Raphael Hertzog wrote:
> I tried 2.6.17.7.
>
> But I'm really not sure that the 2.6 is a regression from 2.4, in fact I
> think it does better by default.
>
> The stock 2.4.31 kernel I was using had serial overruns at 9600 bauds
> already. Once patched with the low latency/preemptive kernel patchs, it
> was way better and I had only overruns at 115200 bauds.
>
> With the 2.6.17.7 kernel (configured with CONFIG_PREEMPT and
> CONFIG_HZ=1000), I'm seeing overruns starting at 38400 bauds. So
> compared to plain 2.4, it's better. However compared to the patched
> 2.4, it's worse.
This tells me your issue is not a problem with the
serial or tty code, but rather a matter of IRQ latency.
(Which you may have already known, but I was unclear on)
I do not expect 2.6.18-rc4 to make a difference.
For fun, have you tried playing with the rx FIFO trigger
level in the 16550A entry in drivers/serial/8250.c ?
You could try replacing UART_FCR_R_TRIG_10 (8 char trigger)
with UART_FCR_R_TRIG_01 (4 char trigger) or even
UART_FCR_R_TRIG_00 (1 char trigger).
That creates more interrupts, but allows
more time to activate the ISR before overrun.
Lee's issue may still merit investigation into the
serial/tty code.
--
Paul Fulghum
Microgate Systems, Ltd.
next prev parent reply other threads:[~2006-08-17 16:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 10:45 How to avoid serial port buffer overruns? Raphael Hertzog
2006-08-16 14:31 ` Lennart Sorensen
2006-08-16 14:57 ` Raphael Hertzog
2006-08-16 18:44 ` Lee Revell
2006-08-16 19:23 ` Paul Fulghum
2006-08-16 21:12 ` Lee Revell
2006-08-16 22:24 ` Paul Fulghum
2006-08-16 23:10 ` Russell King
2006-08-16 23:15 ` Lee Revell
2006-08-16 23:19 ` Russell King
2006-08-16 23:28 ` Lee Revell
2006-08-17 0:15 ` R: " Giampaolo Tomassoni
2006-08-18 8:48 ` Giampaolo Tomassoni
2006-08-18 17:00 ` Lee Revell
2006-08-18 17:04 ` Russell King
2006-08-18 17:30 ` Lee Revell
2006-08-18 18:34 ` Russell King
2006-08-18 18:52 ` Lee Revell
2006-08-18 19:01 ` Russell King
2006-08-18 19:07 ` Russell King
2006-08-18 19:09 ` Lee Revell
2006-08-17 9:20 ` Alan Cox
2006-08-17 9:28 ` Russell King
2006-08-17 11:57 ` Alan Cox
2006-08-17 13:29 ` Paul Fulghum
2006-08-17 15:48 ` Raphael Hertzog
2006-08-17 16:10 ` Raphael Hertzog
2006-08-17 16:40 ` Paul Fulghum [this message]
2006-08-18 19:31 ` Lee Revell
2006-08-23 12:45 ` Raphael Hertzog
[not found] <fa.AByCsBI8k71hMVzCyQVimrLiDU4@ifi.uio.no>
2006-08-16 14:35 ` Robert Hancock
2006-08-16 14:42 ` Erik Mouw
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=44E49C0F.7030600@microgate.com \
--to=paulkf@microgate.com \
--cc=hertzog@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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