From: Paul Fulghum <paulkf@microgate.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
johannes@erdfelt.com,
USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: Test Patch: 2.5.69 Interrupt Latency
Date: 16 May 2003 13:31:40 -0500 [thread overview]
Message-ID: <1053109899.2606.46.camel@toshiba> (raw)
In-Reply-To: <1053107295.2606.21.camel@toshiba>
On Fri, 2003-05-16 at 12:48, Paul Fulghum wrote:
> So always allowing suspend, and selectively doing the
> wakeup will cause:
> 1. thrashing for case of one port OC,
> other port OK with attached device.
> 2. prevent port with OC from doing resume
> after clearing OC condition.
>
> For the case of all ports hardwired OC, this
> will work because you suspend the whole controller
> and never get a valid resume.
Just to add another argument to disallowing suspend
instead of qualifying wakeup:
In 99% of cases, with no OC, this won't come into play.
In .9% of cases, with transient OC, this won't delay suspend long.
In .01% of cases, with all hardwired OC ports, suspend does not matter.
Plus it cures the above problems #1 and #2.
If problem #1 occurs, I don't see that thrashing is
any better than not suspending at all.
--
Paul Fulghum
paulkf@microgate.com
next prev parent reply other threads:[~2003-05-16 18:19 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 16:12 2.5.69 Interrupt Latency Paul Fulghum
2003-05-07 19:41 ` Paul Fulghum
2003-05-07 22:28 ` Andrew Morton
2003-05-08 0:25 ` Paul Fulghum
2003-05-08 13:56 ` Paul Fulghum
2003-05-08 19:22 ` Andrew Morton
2003-05-08 19:35 ` Paul Fulghum
2003-05-08 23:20 ` Brian Gerst
2003-05-09 18:12 ` Paul Fulghum
2003-05-09 20:30 ` Paul Fulghum
2003-05-09 21:28 ` Andrew Morton
2003-05-12 13:57 ` Paul Fulghum
2003-05-12 14:06 ` Paul Fulghum
2003-05-12 16:24 ` Greg KH
2003-05-12 17:08 ` Paul Fulghum
2003-05-12 17:30 ` Greg KH
2003-05-12 17:49 ` Paul Fulghum
2003-05-12 18:01 ` Greg KH
2003-05-12 18:15 ` Paul Fulghum
2003-05-13 15:26 ` Alan Stern
2003-05-13 15:35 ` Paul Fulghum
2003-05-13 17:30 ` Greg KH
2003-05-13 13:01 ` Paul Fulghum
2003-05-13 18:09 ` Greg KH
2003-05-13 18:11 ` Greg KH
2003-05-13 21:35 ` Alan Stern
2003-05-13 21:48 ` Helge Hafting
2003-05-13 22:09 ` Alan Stern
2003-05-14 21:06 ` Paul Fulghum
2003-05-14 21:15 ` Johannes Erdfelt
2003-05-14 21:30 ` Greg KH
2003-05-14 21:45 ` Paul Fulghum
2003-05-13 20:17 ` Bill Davidsen
2003-05-13 22:39 ` Paul Fulghum
2003-05-14 20:52 ` Test Patch: " Alan Stern
2003-05-15 13:45 ` Paul Fulghum
2003-05-15 14:12 ` Paul Fulghum
2003-05-15 21:07 ` Alan Stern
2003-05-15 15:26 ` Paul Fulghum
2003-05-15 18:11 ` Alan Stern
2003-05-15 18:40 ` Paul Fulghum
2003-05-15 19:42 ` Paul Fulghum
2003-05-15 19:59 ` Paul Fulghum
2003-05-15 21:13 ` Alan Stern
2003-05-15 21:30 ` Paul Fulghum
2003-05-15 19:17 ` Paul Fulghum
2003-05-16 15:33 ` Alan Stern
2003-05-16 15:58 ` Paul Fulghum
2003-05-16 16:18 ` Paul Fulghum
2003-05-16 17:16 ` Alan Stern
2003-05-16 17:48 ` Paul Fulghum
2003-05-16 18:31 ` Paul Fulghum [this message]
2003-05-16 18:40 ` Alan Stern
2003-05-16 19:05 ` Paul Fulghum
2003-05-18 0:57 ` Andrew McGregor
2003-05-16 17:20 ` Alan Stern
2003-05-16 17:51 ` Paul Fulghum
2003-05-19 16:41 ` Alan Stern
2003-05-19 18:20 ` Paul Fulghum
2003-05-19 18:49 ` Alan Stern
2003-05-16 18:10 ` Paul Fulghum
2003-05-14 17:50 ` Paul Fulghum
2003-05-09 21:07 ` Andrew Morton
2003-05-09 21:28 ` Paul Fulghum
2003-05-08 14:47 ` Paul Fulghum
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=1053109899.2606.46.camel@toshiba \
--to=paulkf@microgate.com \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.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;
as well as URLs for NNTP newsgroup(s).