From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Ray Lee <madrabbit@gmail.com>,
Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dominik Brodowski <linux@brodo.de>,
John Stultz <johnstul@us.ibm.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [patch] fix delay_tsc (was Re: delay_tsc(): inefficient delay loop (2.6.16-mm1))
Date: Mon, 27 Mar 2006 01:18:52 +0200 [thread overview]
Message-ID: <200603270118.53102.ak@suse.de> (raw)
In-Reply-To: <200603261647_MC3-1-BB98-CB09@compuserve.com>
> I'm running a system with this applied now. I think there are still
> problems if someone uses huge delays, though. What keeps someone from
> trying to delay for > 2^31 cycles?
You shouldn't. The caller has a compile time check for that. And if you pass
in dynamic values you get what you deserve.
-Andi
next prev parent reply other threads:[~2006-03-27 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 21:44 Chuck Ebbert
2006-03-26 23:18 ` Andi Kleen [this message]
2006-03-27 0:42 ` Ray Lee
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=200603270118.53102.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=madrabbit@gmail.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
all inboxes | Powered by JetHome®