From: Michael Ellerman <michael@ellerman.id.au>
To: will_schmidt@vnet.ibm.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] hvc_console polling mode timer backoff
Date: Sun, 15 Apr 2007 23:33:32 +1000 [thread overview]
Message-ID: <1176644012.5422.3.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <1176491513.28514.66.camel@farscape.rchland.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]
On Fri, 2007-04-13 at 14:11 -0500, Will Schmidt wrote:
> On Fri, 2007-13-04 at 17:47 +1000, Michael Ellerman wrote:
> > Because this is a super tight performance critical inner loop I've
> > changed it to use a shift instead of divide. So now it's more like 1.5%,
> > but still the point is it increases faster as time passes.
>
> Using a shift here is a good idea. I had considered accelerating the
> backoff value, but it got more complex than I wanted quickly.. I didnt
> consider a shift. :-)
>
> > It'd be good if some more people can bang on this and see what they
> > think of the interactivity.
>
> Still works OK on my power4. I can see the delay on my console, but
> I'm specifically looking for it, I don't think it's an issue.
Cool. Yeah I think people will hardly notice it unless they're trying to
t notice it.
> > +#include <linux/debugfs.h>
> > +static int hvc_debug_init(void)
> > +{
> > + debugfs_create_u32("hvc_timeout", 0400, NULL, &timeout);
> > + return 0;
> > +}
> > +__initcall(hvc_debug_init);
> > +
>
> Is this part temporary for your graphing, or think it's something that
> should go in?
No that's just debug foobar I used for the graphs, I'll send a cleaned
up version during the week if you don't beat me to it.
> I used /proc/timer_stats output for my graphing, just dont have a good
> public spot to upload the pics..
Time to get a blag! ;)
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-15 13: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 ` [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 [this message]
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=1176644012.5422.3.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--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 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).