From: William Hubbs <w.d.hubbs@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: CPU issues with Speakup
Date: Fri, 29 May 2009 12:02:05 -0500 [thread overview]
Message-ID: <20090529170205.GA7325@linux1> (raw)
In-Reply-To: <20090529160907.TBHZ14603.eastrmmtao102.cox.net@eastrmimpo01.cox.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, May 29, 2009 at 11:12:39AM -0500, Chris Brannon wrote:
> I am attaching the output from an execution of "powertop -d" on my
> system. During this run, espeakup had an average of 1669.1 wakeups / second.
Ok, I know what is happening here. Espeakup is using a select() call to
read the softsynth with a timeout of 1 microsecond, so that would be
about right. The issue is with espeakup, not speakup. I will take a
look at how I am using the select call.
> PowerTOP 1.11 (C) 2007, 2008 Intel Corporation
>
> Collecting data for 15 seconds
>
>
> < Detailed C-state information is not available.>
> P-states (frequencies)
> Wakeups-from-idle per second : 2075.9 interval: 15.0s
> no ACPI power usage estimate available
> Top causes for wakeups:
> 80.4% (1669.1) espeakup : hrtimer_start_range_ns (hrtimer_wakeup)
> 14.9% (309.2) <interrupt> : VIA8237
> 2.5% ( 51.1) <interrupt> : ra0
> 1.3% ( 26.3) <kernel core> : hrtimer_start_range_ns (tick_sched_timer)
> 0.4% ( 8.0) <kernel module> : usb_hcd_poll_rh_status (rh_timer_func)
> 0.2% ( 3.3) <interrupt> : PS/2 keyboard/mouse/touchpad
> 0.1% ( 2.0) <kernel core> : clocksource_register (clocksource_watchdog)
> 0.1% ( 1.5) emacs : synth_printf (thread_wake_up)
> 0.0% ( 1.0) dhcpcd : MlmeInit (MlmePeriodicExec)
> 0.0% ( 0.3) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_timer)
> 0.0% ( 0.3) <kernel module> : neigh_table_init_no_netlink (neigh_periodic_timer)
> 0.0% ( 0.2) <interrupt> : sata_via
> 0.0% ( 0.2) init : hrtimer_start_range_ns (hrtimer_wakeup)
> 0.0% ( 0.2) <kernel core> : page_writeback_init (wb_timer_fn)
> 0.0% ( 0.1) kinit : start_this_handle (commit_timeout)
> 0.0% ( 0.1) events/0 : queue_delayed_work (delayed_work_timer_fn)
> 0.0% ( 0.1) mpd : announce_edge (kd_nosound)
> 0.0% ( 0.1) <kernel core> : announce_edge (kd_nosound)
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
iEYEARECAAYFAkogFQ0ACgkQblQW9DDEZTh2hwCghbU6ciU8uU8gyqxf96VRkIWC
GKMAn1TKtI5ebj4R1YGs6A/itNHMqYUV
=/8v2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Hermann
` Kirk Reiser
` Hermann
` Samuel Thibault
` Hermann
` Chris Brannon
` William Hubbs [this message]
` Kerry Hoath
` Kirk Reiser
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=20090529170205.GA7325@linux1 \
--to=w.d.hubbs@gmail.com \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).