From: "Luck, Tony" <tony.luck@intel.com>
To: Andi Kleen <ak@muc.de>
Cc: akpm@osdl.org, linux-arch@vger.kernel.org, mingo@elte.hu
Subject: Re: [patch 1/1] Fix spinlock debugging delays to not time out too early
Date: Tue, 7 Feb 2006 10:44:35 -0800 [thread overview]
Message-ID: <20060207184435.GA18589@agluck-lia64.sc.intel.com> (raw)
In-Reply-To: <200602071929.24762.ak@muc.de>
On Tue, Feb 07, 2006 at 07:29:24PM +0100, Andi Kleen wrote:
> For this case that would be ok, as long as it isn't a hour or so,
> but let's say < 1 minute.
About 9.7 seconds on ia64 for:
for (i = 0; i < loops_per_jiffy * HZ; i++) {
__delay(1);
}
so yes, well under a minute.
-Tony
next prev parent reply other threads:[~2006-02-07 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 18:20 [patch 1/1] Fix spinlock debugging delays to not time out too early Luck, Tony
2006-02-07 18:29 ` Andi Kleen
2006-02-07 18:44 ` Luck, Tony [this message]
2006-02-07 19:14 ` Ingo Molnar
2006-02-07 19:37 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-02-07 17:41 akpm
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=20060207184435.GA18589@agluck-lia64.sc.intel.com \
--to=tony.luck@intel.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=mingo@elte.hu \
/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