From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] hrtimers: Special-case zero length sleeps
Date: Wed, 15 Feb 2012 20:47:57 +0000 [thread overview]
Message-ID: <20120215204757.GA30275@srcf.ucam.org> (raw)
In-Reply-To: <alpine.LFD.2.02.1202152140110.2794@ionos>
On Wed, Feb 15, 2012 at 09:46:27PM +0100, Thomas Gleixner wrote:
> Dammit, we cannot come up with a reasonable definition for special
> casing that stuff simply because you cannot draw a clear boundary what
> to special case and what not. And there is no sensible definition for
> what to do - return right away or go through schedule() or what ever.
>
> sleep(0) is as pointless as sched_yield() and it's about time that we
> stop to create a fucking mess in the kernel just because user space
> programmers refuse to understand how an operating system works and how
> proper programming should be done.
Ok. I'll work on finding how prevelant it is and see if we can kill it
off in userspace.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-02-15 20:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 14:59 [PATCH] hrtimers: Special-case zero length sleeps Matthew Garrett
2012-02-15 14:40 ` Thomas Gleixner
2012-02-15 14:52 ` Matthew Garrett
2012-02-15 20:14 ` Thomas Gleixner
2012-02-15 20:22 ` Matthew Garrett
2012-02-15 20:30 ` Thomas Gleixner
2012-02-15 20:38 ` Matthew Garrett
2012-02-15 20:40 ` Peter Zijlstra
2012-02-15 20:43 ` Matthew Garrett
2012-02-15 20:46 ` Thomas Gleixner
2012-02-15 20:47 ` Matthew Garrett [this message]
2012-02-16 14:27 ` Matthew Garrett
2012-02-16 14:31 ` Alan Cox
2012-02-16 14:51 ` Peter Zijlstra
2012-02-16 15:01 ` Matthew Garrett
2012-02-16 19:09 ` Thomas Gleixner
2012-02-15 14:54 ` Peter Zijlstra
2012-02-15 14:58 ` Matthew Garrett
2012-02-15 20:22 ` 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=20120215204757.GA30275@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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.