From: Pavel Machek <pavel@ucw.cz>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: Patrick Pannuto <ppannuto@codeaurora.org>,
linux-kernel@vger.kernel.org, sboyd@codeaurora.org,
tglx@linutronix.de, mingo@elte.hu, heiko.carstens@de.ibm.com,
eranian@google.com, schwidefsky@de.ibm.com,
linux-arm-msm@vger.kernel.org
Subject: Re: [RFC] [PATCH] timer: Added usleep[_range][_interruptable] timer
Date: Sat, 26 Jun 2010 23:43:59 +0200 [thread overview]
Message-ID: <20100626214359.GA1773@elf.ucw.cz> (raw)
In-Reply-To: <1277326605.15159.70.camel@c-dwalke-linux.qualcomm.com>
Hi!
> > Yes, this test was leftover from a different project that involved refactoring
> > timers, so it was available and easy. My guess for the reduction in number of
> > wakeups is that the processor is able to do other work during the 100us it was
> > previously busy-waiting, and thus had to wake up less often.
>
> As I said in the prior email the udelay()'s don't preclude other types
> of work since you can get preempted.
Yes, you can get preempted, but you'll still spin in the tight loop
counting...
So it does not preclude other task, but then you'll spin
unneccessarily.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2010-06-26 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C225EED.5040600@codeaurora.org>
2010-06-23 20:05 ` [RFC] [PATCH] timer: Added usleep[_range][_interruptable] timer Daniel Walker
2010-06-23 20:21 ` Patrick Pannuto
2010-06-23 20:56 ` Daniel Walker
2010-06-23 22:04 ` Andreas Mohr
2010-06-26 21:43 ` Pavel Machek [this message]
2010-06-28 18:03 ` Patrick Pannuto
2010-06-28 19:39 ` Daniel Walker
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=20100626214359.GA1773@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=dwalker@codeaurora.org \
--cc=eranian@google.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ppannuto@codeaurora.org \
--cc=sboyd@codeaurora.org \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
/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).