public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Ross Biro <ross.biro@gmail.com>
Cc: linux-kerneL@vger.kernel.org
Subject: Re: [PATCH 2.6.14] X86_64 delay resolution
Date: 09 Dec 2005 16:24:26 -0700	[thread overview]
Message-ID: <p73slt1q2fp.fsf@verdi.suse.de> (raw)
In-Reply-To: <8783be660512090834l40b5c051p6c58676bccc834fc@mail.gmail.com>

Ross Biro <ross.biro@gmail.com> writes:

> On x86_64 smp systems, we noticed that the amount of time udelay would
> spin for varied from cpu to cpu.  In our test case, udelay(10) would
> only delay for 9.7us on some cpus while on others it would delay for
> the full 10us.  We tracked the problem down to an unnecessary attempt
> to avoid arithmetic overflow.  Here's a fix complete with an overly
> verbose comment.

I applied it without the comment and without the extra sets
of brackets. Please submit future x86-64 patches directly
to me and also Signed them off and use toplevel diffs.

Thanks,
-Andi

      reply	other threads:[~2005-12-09 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 16:34 [PATCH 2.6.14] X86_64 delay resolution Ross Biro
2005-12-09 23:24 ` Andi Kleen [this message]

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=p73slt1q2fp.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=linux-kerneL@vger.kernel.org \
    --cc=ross.biro@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