From: Theodore Tso <tytso@mit.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: George Spelvin <linux@horizon.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC 2/2] serial/8250.c: Use self-adjusting list for port poll order.
Date: Fri, 14 Nov 2008 19:10:13 -0500 [thread overview]
Message-ID: <20081115001013.GM25117@mit.edu> (raw)
In-Reply-To: <20081114214711.3c1d1473@lxorguk.ukuu.org.uk>
On Fri, Nov 14, 2008 at 09:47:11PM +0000, Alan Cox wrote:
> > This code does that by using the previous poll cycles as a hint.
> > If a port is idle, it will migrate to the end of the list and
> > only have to be checked once.
> >
> > Part 1 changed the list to singly-linked to make the list shuffling easier.
> >
> > Comments? Please?
>
> Is it really worth the complexity
>
> - PCI ports are shared IRQ always
> - Legacy ports are almost never shared IRQ on the LPC bus (and are
> increasingly going away)
It's worth the complexity only *if* you have enough ports shared on a
single IRQ and simultaneously such that there a risk that if you don't
poll them quickly enough, characters will actually get dropped from
the UART's FIFO. The question is whether that is likely to happen on
modern CPU's. I worred about such things when I tried to make 16
115kbps serial ports work at full-speed using relatively primitive
16550A UART's with 16 character FIFO's on a 40 MHz 386. But (a)
UART's generally have deeper FIFO's these days, and (b) CPU's have
gotten a wee bit faster since 1992.
So color me dubious that this is actually necessary....
- Ted
next prev parent reply other threads:[~2008-11-15 0:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081113150308.3590.qmail@science.horizon.com>
[not found] ` <20081114053042.11532.qmail@science.horizon.com>
2008-11-14 21:17 ` [RFC 1/2] serial/8250.c: Change to singly linked handler chain George Spelvin
[not found] ` <20081114053314.12093.qmail@science.horizon.com>
2008-11-14 21:34 ` [RFC 2/2] serial/8250.c: Use self-adjusting list for port poll order George Spelvin
2008-11-14 21:47 ` Alan Cox
2008-11-15 0:10 ` Theodore Tso [this message]
2008-11-16 15:23 ` George Spelvin
2008-11-16 15:51 ` Alan Cox
2008-11-16 16:57 ` George Spelvin
2008-11-16 16:23 ` Theodore Tso
2008-11-16 18:02 ` George Spelvin
2008-11-16 16:49 ` Theodore Tso
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=20081115001013.GM25117@mit.edu \
--to=tytso@mit.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.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