From: "Manu Abraham" <abraham.manu@gmail.com>
To: "Roman Zippel" <zippel@linux-m68k.org>
Cc: "Arjan van de Ven" <arjan@infradead.org>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-kernel@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>,
akpm@linux-foundation.org, "Ingo Molnar" <mingo@elte.hu>
Subject: Re: [PATCH] msleep() with hrtimers
Date: Mon, 6 Aug 2007 14:20:10 +0400 [thread overview]
Message-ID: <1a297b360708060320m2e9aa419n1f043fb18d987850@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708061159370.1817@scrub.home>
On 8/6/07, Roman Zippel <zippel@linux-m68k.org> wrote:
> Hi,
>
> On Sun, 5 Aug 2007, Arjan van de Ven wrote:
>
> > > There's no problem to provide a high resolution sleep, but there is also
> > > no reason to mess with msleep, don't fix what ain't broken...
> >
> > John Corbet provided the patch because he had a problem with the current
> > msleep... in that it didn't provide as good a common case as he
> > wanted... so I think your statement is wrong ;)
>
> Only under the assumptation, that msleep _must_ be "fixed" for all other
> current users too.
> Give users a choice to use msleep or nanosleep, how do you know what's
> "best" for them?
>
You mean to say, the granularity of msleep is in mS with a tolerance
of +/- "n" mS whereas nanosleep would have the tolerance in nS ?
(ignoring all the discussions about hrtimers and their internal
design)
I guess many people are/were confused on the aspect that, a msleep(1)
meant sleep for a 1mS and nothing more. Well, this would explain, some
of my hair raising incidents, if i understood you correctly.
Since it is such a confusion, maybe it needs to be documented some
place, that people don't fall into the same trap.
Manu
next prev parent reply other threads:[~2007-08-06 10:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 18:37 [PATCH] msleep() with hrtimers Jonathan Corbet
2007-08-03 18:54 ` Ingo Molnar
2007-08-03 19:19 ` Roman Zippel
2007-08-03 19:46 ` Arjan van de Ven
2007-08-03 19:58 ` Roman Zippel
2007-08-03 23:53 ` Arjan van de Ven
2007-08-04 3:00 ` Roman Zippel
2007-08-04 19:19 ` Arjan van de Ven
2007-08-06 0:09 ` Roman Zippel
2007-08-06 0:43 ` Arjan van de Ven
2007-08-06 1:03 ` Roman Zippel
2007-08-06 5:39 ` Arjan van de Ven
2007-08-06 10:03 ` Roman Zippel
2007-08-06 10:20 ` Manu Abraham [this message]
2007-08-06 15:53 ` Arjan van de Ven
2007-08-07 10:40 ` Manu Abraham
2007-08-07 12:45 ` Roman Zippel
2007-08-08 4:15 ` Arjan van de Ven
2007-08-09 19:31 ` Denis Vlasenko
2007-08-09 20:01 ` Denis Vlasenko
2007-08-07 19:40 ` Andrew Morton
2007-08-07 23:16 ` Roman Zippel
2007-08-07 23:29 ` Andrew Morton
2007-08-08 3:47 ` Roman Zippel
2007-08-08 4:14 ` Andrew Morton
2007-08-09 22:31 ` Roman Zippel
2007-08-08 11:55 ` Andi Kleen
2007-08-08 11:09 ` Manu Abraham
2007-08-08 11:52 ` Andi Kleen
2007-08-08 11:59 ` Manu Abraham
2007-08-09 7:16 ` Andrew Morton
2007-08-09 15:08 ` [linux-usb-devel] " Alan Stern
2007-11-28 10:29 ` Andrew Morton
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=1a297b360708060320m2e9aa419n1f043fb18d987850@mail.gmail.com \
--to=abraham.manu@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).