public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@innominate.de>
To: Timur Tabi <ttabi@interactivesi.com>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Kernel Janitor's TODO list
Date: Wed, 31 Jan 2001 01:06:08 +0100	[thread overview]
Message-ID: <3A7756F0.8B589FC7@innominate.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0101291018080.5353-100000@ns-01.hislinuxbox.com>  	<Pine.LNX.4.21.0101291018080.5353-100000@ns-01.hislinuxbox.com> <Mdiqd.A.qe.yEvd6@dinero.interactivesi.com>

Timur Tabi wrote:
> 
> ** Reply to message from David Woodhouse
> 
> > Note that this is _precisely_ the reason I'm advocating the removal of
> > sleep_on(). When I was young and stupid (ok, "younger and stupider") I used
> > sleep_on() in my code. I pondered briefly the fact that I really couldn't
> > convince myself that it was safe, but because it was used in so many other
> > places, I decided I had to be missing something, and used it anyway.
> >
> > I was wrong. I was copying broken code. And now I want to remove all those
> > bad examples - for the benefit of those who are looking at them now and are
> > tempted to copy them.
> 
> What is wrong with sleep_on()?

If you have a task that looks like:

    loop:
        <do something important>
        sleep_on(q)

And you do wakeup(q) hoping to get something important done, then if the
task isn't sleeping at the time of the wakeup it will ignore the wakeup
and go to sleep, which imay not be what you wanted.

--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-31  0:08 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-28 16:14 [ANNOUNCE] Kernel Janitor's TODO list Manfred Spraul
2001-01-28 14:36 ` Arnaldo Carvalho de Melo
2001-01-28 16:45   ` Manfred Spraul
2001-01-28 17:07     ` David Woodhouse
2001-01-28 17:40       ` Manfred Spraul
2001-01-28 18:51         ` Roman Zippel
2001-01-29 17:01         ` Timur Tabi
2001-01-29 17:10           ` John Levon
2001-01-29 18:27             ` David D.W. Downey
2001-01-29 20:44               ` davej
2001-01-29 20:51               ` Timur Tabi
2001-01-29 20:56                 ` Rasmus Andersen
2001-01-30  0:29                 ` Peter Samuelson
2001-01-30  0:20               ` Ingo Oeser
2001-01-30 11:11               ` David Woodhouse
2001-01-30 16:52               ` Timur Tabi
2001-01-31  0:06                 ` Daniel Phillips [this message]
2001-01-31  0:09                 ` Timur Tabi
2001-01-31  9:14                   ` David Woodhouse
2001-01-30 17:10               ` David Woodhouse
2001-01-29 17:26           ` Andi Kleen
2001-01-29 19:47             ` Roman Zippel
2001-01-29 20:35               ` Andi Kleen
2001-02-16 14:29                 ` Andrea Arcangeli
2001-02-16 14:26               ` Andrea Arcangeli
2001-01-31 17:57         ` Alan Cox
2001-01-31 19:15           ` Manfred Spraul
  -- strict thread matches above, loose matches on Subject: below --
2001-01-30  1:22 Rusty Russell
2001-01-30  3:08 ` Andrew Morton
2001-01-27 17:11 Arnaldo Carvalho de Melo
2001-01-28 15:20 ` David Woodhouse
2001-01-28 14:03   ` Arnaldo Carvalho de Melo
2001-01-28 15:49   ` Michael H. Warfield
2001-01-28 16:13 ` Andrew Morton
2001-01-28 14:28   ` Arnaldo Carvalho de Melo
2001-01-28 14:33     ` Arnaldo Carvalho de Melo
2001-01-30  1:05   ` Rusty Russell
2001-01-30 11:19     ` Daniel Phillips
2001-01-30 17:49       ` Daniel Phillips

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=3A7756F0.8B589FC7@innominate.de \
    --to=phillips@innominate.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ttabi@interactivesi.com \
    /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