From: Milton Miller <miltonm@bga.com>
To: Michael Ellerman <michael@ellerman.id.au>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Cc: Olof Johansson <olof@lixom.net>, ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] hvc_console polling mode timer backoff
Date: Sat, 14 Apr 2007 14:42:02 -0500 [thread overview]
Message-ID: <97762565fcdccbf85d1d04cd055b1197@bga.com> (raw)
In-Reply-To: <1176450459.4734.32.camel@concordia.ozlabs.ibm.com>
Michael Ellerman wrote:
> + * msleep until we reach the max. This may be noticable as a brief
> (average
> + * one second) delay on the console before the console responds to
> input when
> + * there has been no input for sometime.
> + */
> +#define MIN_TIMEOUT (10)
> +#define MAX_TIMEOUT (2000)
> +static u32 timeout = MIN_TIMEOUT;
Did you consider making MAX_TIMEOUT a module parameter? It could then
be changed at runtime through /sys/modules/.
> +
> + if (timeout < MAX_TIMEOUT)
> + timeout += (timeout >> 6) + 1;
Keeping MIN_TIMEOUT a define is okay with me, and the code will
naturally ignore max < MIN. It may overshoot timeout by 1/64th.
I doubt we would worry about the overflow case, because by then
the timeout would have been quite long, and the user would like
it to be short again.
milton
next prev parent reply other threads:[~2007-04-14 19:42 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 ` [PATCH] hvc_console polling mode timer backoff Linas Vepstas
2007-04-12 18:43 ` 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 [this message]
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=97762565fcdccbf85d1d04cd055b1197@bga.com \
--to=miltonm@bga.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=olof@lixom.net \
--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 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).