From: Jonathan Corbet <corbet@lwn.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
NeilBrown <neilb@suse.de>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
"Dr. H. Nikolaus Schaller" <hns@goldelico.com>,
Marek Belisko <marek@goldelico.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH/RFC] wait_for_completion_timeout() considered harmful.
Date: Mon, 18 Nov 2013 17:49:02 -0700 [thread overview]
Message-ID: <20131118174902.312d8fa6@lwn.net> (raw)
In-Reply-To: <20131118234209.GO16796@laptop.programming.kicks-ass.net>
On Tue, 19 Nov 2013 00:42:09 +0100
Peter Zijlstra <peterz@infradead.org> wrote:
> I briefly talked to Thomas about this earlier today and we need to fix
> this at a lower level -- the quick 'n dirty solution is to add 1 jiffy
> down in the timer-wheel when we enqueue these things.
That can lead to situations like the one I encountered years ago where
msleep(1) would snooze for 20ms. I didn't get much love for my idea of
switching msleep() to hrtimers back then, but I still think it might be be
better to provide the resolution that the interface appears to promise.
jon
next prev parent reply other threads:[~2013-11-19 0:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 21:06 [PATCH/RFC] wait_for_completion_timeout() considered harmful NeilBrown
2013-11-18 23:27 ` Andrew Morton
2013-11-18 23:42 ` Peter Zijlstra
2013-11-19 0:49 ` Jonathan Corbet [this message]
2013-11-19 7:05 ` Ingo Molnar
2013-11-19 8:29 ` Peter Zijlstra
2013-11-18 23:44 ` NeilBrown
2013-11-19 8:25 ` Peter Zijlstra
2013-11-19 8:58 ` NeilBrown
2013-11-19 12:23 ` Peter Zijlstra
2013-11-19 14:39 ` 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=20131118174902.312d8fa6@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=hns@goldelico.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marek@goldelico.com \
--cc=mingo@redhat.com \
--cc=neilb@suse.de \
--cc=peterz@infradead.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.