All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Patrick Pannuto <ppannuto@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
	akpm@linux-foundation.org, mingo@elte.hu, akinobu.mita@gmail.com,
	sboyd@codeaurora.org
Subject: Re: [PATCH] timer: Added usleep[_range] timer
Date: Mon, 19 Jul 2010 15:22:19 -0700	[thread overview]
Message-ID: <4C44D01B.6090508@linux.intel.com> (raw)
In-Reply-To: <4C44CDD2.1070708@codeaurora.org>

On 7/19/2010 3:12 PM, Patrick Pannuto wrote:
>    
>> I like the general idea, but I kinda doubt the "interruptible" version
>> makes sense for this...
>> do you have any users for that in mind? if not... can we leave the
>> interruptible version out... makes it simpler by a lot.
>>
>>      
> Respun without interruptible...
>
>
>  From 08b717cf4f76d7578cb20c1b1444d89a9331ce02 Mon Sep 17 00:00:00 2001
> From: Patrick Pannuto<ppannuto@codeaurora.org>
> Date: Mon, 19 Jul 2010 15:09:26 -0700
> Subject: [PATCH] timer: Added usleep[_range] timer
>
> usleep[_range] are finer precision implementations of msleep
> and are designed to be drop-in replacements for udelay where
> a precise sleep / busy-wait is unnecessary. They also allow
> an easy interface to specify slack when a precise (ish)
> wakeup is unnecessary to help minimize wakeups
>
>    

excellent

Acked-by: Arjan van de Ven <arjan@linux.intel.com>


  reply	other threads:[~2010-07-19 22:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 20:54 [PATCH] timer: Added usleep[_range][_interruptible] timer Patrick Pannuto
2010-07-19 22:05 ` Arjan van de Ven
2010-07-19 22:12   ` [PATCH] timer: Added usleep[_range] timer Patrick Pannuto
2010-07-19 22:22     ` Arjan van de Ven [this message]
2010-07-22 23:16     ` Andrew Morton
2010-07-23 13:10     ` [tip:timers/core] " tip-bot for Patrick Pannuto

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=4C44D01B.6090508@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=ppannuto@codeaurora.org \
    --cc=sboyd@codeaurora.org \
    --cc=tglx@linutronix.de \
    /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.