mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PATCH: add framework for ndelay (nanoseconds)
Date: 06 Feb 2003 15:53:05 +0000	[thread overview]
Message-ID: <1044546783.10374.4.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20030206174944.A17905@jurassic.park.msu.ru>

On Thu, 2003-02-06 at 14:49, Ivan Kokshaysky wrote:
> > Wouldn't it make more sense to call the parameter `nsecs' (or `ns')?
> 
> There are more serious problems with this implementation:
> 1) It's *very* imprecise. Even on an 1 GHz CPU and with HZ = 100 precision
>    is ~86 nsec. With HZ = 1000 it's almost unusable on *any* CPU.

HZ = 1000 isn't a 2.4 thing.

> As of current 2.4, there is the only user of ndelay() - ide_execute_command()
> that calls ndelay(400). Why udelay(1) cannot be used instead?

Why waste 500nS every IDE command as opposed to doing the job right ? The initial
ndelay() is a quick implementation. If you don't like it implement a better one,
if your box isnt fast implement it as udelay.

In the 2.5 tree I also hope we can avoid the ndelay in some cases

Alan


  reply	other threads:[~2003-02-06 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200302040533.h145Xqq19457@hera.kernel.org>
2003-02-05 14:34 ` Geert Uytterhoeven
2003-02-06 14:49   ` Ivan Kokshaysky
2003-02-06 15:53     ` Alan Cox [this message]
2003-02-06 15:05       ` Ivan Kokshaysky
2003-02-06 17:41       ` Ross Biro

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=1044546783.10374.4.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=geert@linux-m68k.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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®