mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Nicholas Mc Guire <hofrat@osadl.org>
Cc: John Stultz <john.stultz@linaro.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] timer: drop the unnecessary while loop in msleep
Date: Mon, 11 Jan 2016 09:15:25 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1601110905180.3575@nanos> (raw)
In-Reply-To: <1452337264-32209-1-git-send-email-hofrat@osadl.org>

On Sat, 9 Jan 2016, Nicholas Mc Guire wrote:

>  The while loop in msleep does not seem necessary as
> timeout is unsigned long and no larger than MAX_JIFFY_OFFSET (which is
> LONG_MAX/2 - 1) so the while-loop condition is always true at the beginning
> (msecs_to_jiffies will return >=0 always and with the +1 timeout is >= 1 so
> the while condition is always true at the start) and
> schedule_timeout_uninterruptible always returns 0, so the while loop always
> terminates after the first loop.

Err, no. schedule_timeout_uninterruptible() can return > 0 when there was a
non timer wakeup. Thinks spurious wakeups. So we need that loop.
 
> Q: what is the purpose of the + 1 offset to the jiffies here ?
> 
> msleep was introduced in 2.6.7 but without the + 1, so with:
> 	unsigned long timeout = msecs_to_jiffies(msecs);
> in 2.6.10-rc2 the msecs_to_jiffies(msecs) + 1; is introduced.
> Nishanth Aravamudan <nacc@us.ibm.com> (https://lkml.org/lkml/2004/11/19/294)
> seems to be the origin while converting msleep to a macro, but no reason
> for the + 1 is given there.

Not really. The +1 was introduced with the following commit:

https://git.kernel.org/cgit/linux/kernel/git/tglx/history.git/commit/kernel/timer.c?id=c259ef842622a5e64418d9dab3b62ee051867edf

Thanks,

	tglx

  reply	other threads:[~2016-01-11  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-09 11:01 Nicholas Mc Guire
2016-01-11  8:15 ` Thomas Gleixner [this message]
2016-01-12 12:48   ` Nicholas Mc Guire
2016-01-12 13:53     ` Thomas Gleixner

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=alpine.DEB.2.11.1601110905180.3575@nanos \
    --to=tglx@linutronix.de \
    --cc=hofrat@osadl.org \
    --cc=john.stultz@linaro.org \
    --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®