From: linas@austin.ibm.com (Linas Vepstas)
To: Will Schmidt <will_schmidt@vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] hvc_console polling mode timer backoff
Date: Thu, 12 Apr 2007 12:33:34 -0500 [thread overview]
Message-ID: <20070412173334.GP4747@austin.ibm.com> (raw)
In-Reply-To: <1176394477.28514.32.camel@farscape.rchland.ibm.com>
On Thu, Apr 12, 2007 at 11:14:36AM -0500, Will Schmidt wrote:
> +/*
> + * timeout will vary between the MIN and MAX values defined here. By default
> + * and during console activity we will use a default MIN_TIMEOUT of 10. When
> + * the console is idle, we increase the timeout value on each pass through
> + * msleep until we reach the max. This may be noticeable as a brief (average
> + * one second) delay on the console before the console responds to input when
> + * there has been no input for some time.
> + */
> +#define MIN_TIMEOUT (10)
> +#define MAX_TIMEOUT (2000)
[...]
> + msleep_interruptible(timeout);
These values are milliseconds (that's what the m in msleep stands for
or at least it did last time I looked). This 10 is 1/100 of a second,
which makes a responsive keyboard for even a very very fast typist.
That's fine. But 2000 is two seconds, which is longer than the amount
of time that I wait before I start panicking that something is broken.
I'd suggest that maybe 1000 or 750 or 500 is more apropriate.
--linas
next prev parent reply other threads:[~2007-04-12 17:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 16:14 [PATCH] hvc_console polling mode timer backoff Will Schmidt
2007-04-12 16:17 ` [PATCH] hvc_console typo corrections Will Schmidt
2007-04-12 17:33 ` Linas Vepstas [this message]
2007-04-12 18:43 ` [PATCH] hvc_console polling mode timer backoff Will Schmidt
2007-04-12 19:09 ` Olof Johansson
2007-04-13 0:45 ` Michael Ellerman
2007-04-13 1:56 ` Olof Johansson
2007-04-13 7:47 ` Michael Ellerman
2007-04-13 16:46 ` Linas Vepstas
2007-04-13 19:11 ` Will Schmidt
2007-04-15 13:33 ` Michael Ellerman
2007-04-16 19:34 ` Will Schmidt
2007-04-14 19:42 ` Milton Miller
2007-04-16 17:03 ` Linas Vepstas
2007-04-16 20:22 ` Will Schmidt
2007-04-16 21:59 ` Linas Vepstas
2007-04-17 0:13 ` Michael Ellerman
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=20070412173334.GP4747@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=will_schmidt@vnet.ibm.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.