From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Paul Fulghum <paulkf@microgate.com>
Cc: Stuart MacDonald <stuartm@connecttech.com>,
"'Russell King'" <rmk+lkml@arm.linux.org.uk>,
"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG][2.6.8.1] serial driver hangs SMP kernel, but not the UPkernel
Date: Mon, 01 Nov 2004 23:02:12 +0000 [thread overview]
Message-ID: <1099350132.18809.73.camel@localhost.localdomain> (raw)
In-Reply-To: <418643E2.9080006@microgate.com>
On Llu, 2004-11-01 at 14:10, Paul Fulghum wrote:
> I was thought it was to speed processing if the
> caller was already in process context. Maybe the
> real intentions are lost to history.
It was added way back by Ted to improve performance when dealing with
low latency requirements for I/O.
> Moving forward, Alan stated that the flip
> routine should not be called in interrupt context.
> His last post concerning some transient state
> of low_latency has confused me.
You were correct about that
next prev parent reply other threads:[~2004-11-02 0:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 19:55 [BUG][2.6.8.1] serial driver hangs SMP kernel, but not the UP kernel Tim_T_Murphy
2004-10-29 20:20 ` Russell King
2004-10-29 22:18 ` Paul Fulghum
2004-10-29 23:40 ` Paul Fulghum
2004-10-30 22:43 ` Alan Cox
2004-10-31 0:26 ` Paul Fulghum
2004-11-01 7:14 ` [BUG][2.6.8.1] serial driver hangs SMP kernel, but not the UPkernel Stuart MacDonald
2004-11-01 14:10 ` Paul Fulghum
2004-11-01 15:12 ` Stuart MacDonald
2004-11-01 23:02 ` Alan Cox [this message]
2004-11-02 0:18 ` Paul Fulghum
2004-10-29 21:08 ` [BUG][2.6.8.1] serial driver hangs SMP kernel, but not the UP kernel Paul Fulghum
-- strict thread matches above, loose matches on Subject: below --
2005-01-10 20:36 [BUG][2.6.8.1] serial driver hangs SMP kernel, but not the UPkernel Tim_T_Murphy
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=1099350132.18809.73.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=stuartm@connecttech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.