mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: Andrew Morton <akpm@osdl.org>,
	Russell King <rmk+lkml@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] deinline sleep/delay functions
Date: Thu, 30 Jun 2005 13:22:53 +0200	[thread overview]
Message-ID: <1120130573.3181.42.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200506301410.43524.vda@ilport.com.ua>


> An if(usec > 2000) { printk(..); dump_stack(); } will do.

that's runtime not compile time.
The old situation was a compile time check which is far more powerful.

> 
> But do you really want to do this? There might be legitimate reasons
> to compute udelay's parameter with results which are sometimes large.

however that's not valid, because a really large udelay parameter will
cause the delay loop math to overflow. That was the main reason for the
"no more than 2ms or so" restriction.
> 
> If you really want to, let's decide on this limit now,

the existing code already has a limit so why not just use that?



  parent reply	other threads:[~2005-06-30 11:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30  5:52 Denis Vlasenko
2005-06-30  8:52 ` Russell King
2005-06-30  9:11   ` Andrew Morton
2005-06-30  9:19     ` Arjan van de Ven
2005-06-30 10:21       ` Denis Vlasenko
2005-06-30 10:47         ` Arjan van de Ven
2005-06-30 11:10           ` Denis Vlasenko
2005-06-30 11:21             ` Russell King
2005-06-30 11:22             ` Arjan van de Ven [this message]
2005-06-30 11:44               ` Denis Vlasenko
2005-06-30 11:57                 ` Maciej W. Rozycki
2005-06-30 12:04                 ` Russell King
2005-06-30 12:20                   ` Denis Vlasenko
2005-07-01  7:54           ` Vojtech Pavlik
2005-06-30  9:44     ` Russell King
2005-07-01  7:53 ` Vojtech Pavlik

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=1120130573.3181.42.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=vda@ilport.com.ua \
    /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®