All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Initial bits to help pull jiffies out of drivers
Date: Tue, 03 Aug 2004 10:27:16 +0200	[thread overview]
Message-ID: <1091521635.2816.7.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040727195939.GA20712@devserv.devel.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

On Tue, 2004-07-27 at 21:59, Alan Cox wrote:
> This is really for comment, the basic idea is to add some relative
> timer functionality. This gives us timeout objects as well as pulling
> jiffies use into one place in the timer code. The need for the old
> interfaces never goes away however because some code uses a previous
> event base to construct timeouts to avoid sliding due to the latency
> between service and re-addition.
> 
> (please cc me on comments)

My gripe with this is that the interface still is relative-to-HZ time.
I'm convinced that driver(writers) are better off with an absolute time
interface, eg add_timeout_ms(), add_timeout_us() etc.
(which btw also give a hint about the accuracy required, so that the
kernel can group milisecond delays together even when they got scheduled
at different usecs, once we get timers that accurate)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-08-03  8:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27 19:59 Initial bits to help pull jiffies out of drivers Alan Cox
2004-08-02 21:33 ` Tim Bird
2004-08-02 21:52   ` Alan Cox
2004-08-03  8:27 ` Arjan van de Ven [this message]
     [not found] <2mGr0-7w6-27@gated-at.bofh.it>
2004-08-02 23:35 ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2004-08-05 13:57 Martin Schwidefsky

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=1091521635.2816.7.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=alan@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.