From: "Chris Doré" <cdore@connecttech.com>
To: linux-serial <linux-serial@vger.kernel.org>
Subject: RE: serial8250_interrupt idea
Date: Mon, 17 Nov 2008 09:08:43 -0500 [thread overview]
Message-ID: <004801c948be$01525990$03f70cb0$@com> (raw)
In-Reply-To: <20081117134504.22912.qmail@science.horizon.com>
> George Spelvin wrote:
> In other words, your step 4/ cannot actually happen.
What if you consider interrupts of higher priority occurring? That could
cause delays in your servicing of X. I've encountered this before with high
speed ports on multiple interrupts, where one port continually steals time
from another.
..Chris
next prev parent reply other threads:[~2008-11-17 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 15:03 serial8250_interrupt idea George Spelvin
2008-11-14 5:30 ` [PATCH 1/2] serial/8250.c: Change to singly linked handler chain George Spelvin
2008-11-14 5:33 ` [PATCH 2/2] serial/8250.c: Use self-adjusting list for port poll order George Spelvin
2008-11-17 9:51 ` serial8250_interrupt idea Tosoni
2008-11-17 10:56 ` George Spelvin
2008-11-17 12:45 ` Tosoni
2008-11-17 13:45 ` George Spelvin
2008-11-17 14:08 ` Chris Doré [this message]
2008-11-17 15:25 ` Tosoni
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='004801c948be$01525990$03f70cb0$@com' \
--to=cdore@connecttech.com \
--cc=linux-serial@vger.kernel.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