From owner-freebsd-mobile Sat Dec 13 00:34:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA05011 for mobile-outgoing; Sat, 13 Dec 1997 00:34:23 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA05005 for ; Sat, 13 Dec 1997 00:34:19 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id SAA01822; Sat, 13 Dec 1997 18:59:05 +1030 (CST) Message-Id: <199712130829.SAA01822@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ken Key cc: freebsd-mobile@FreeBSD.ORG Subject: Re: APM suspend/resume and the "calltodo" timer list. In-reply-to: Your message of "Wed, 10 Dec 1997 11:29:21 CDT." <199712101629.LAA13982@duncan.cs.utk.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Dec 1997 18:59:04 +1030 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi Folks, Hi Ken, sorry I haven't responded before, but I have been thinking about this one a while. > I'm soliciting the mobile community at large for suggestions of things I > may not have thought about that this might negatively effect in the OS. > The worst I have come up with is just that the system potentially could > become very busy at startup time running all the expired timers that have > collapsed together. I think this has been the concern thus far. To be honest, though, I think your point about long timeouts is really quite valid, and the impact of expiring short timeouts in a bunch at resume time is probably, as you suggest, quite low. > I haven't noticed this thus far on my tp560, but I > won't claim having performed an exhaustive analysis. If nothing bad comes > up in this testing, I'll post my patch. That'd be good. I think you're on the right track, FWIW. mike