mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: schedule()
Date: Tue, 26 Feb 2002 15:05:03 -0500	[thread overview]
Message-ID: <3C7BEA6F.97CB8AD4@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020226145622.5179A-100000@chaos.analogic.com>

"Richard B. Johnson" wrote:
> 
> I just read on this list that:
> 
>     while(something)
>     {
>       current->policy |= SCHED_YIELD;
>       schedule();
>     }
> 
> Will no longer be allowed in a kernel module! If this is true, how
> do I loop, waiting for a bit in a port, without wasting CPU time?

Call yield() or better yet, schedule_timeout()

In 2.4, define the above to be yield() in some compatibility module...

-- 
Jeff Garzik      | "UNIX enhancements aren't."
Building 1024    |           -- says /usr/games/fortune
MandrakeSoft     |

  reply	other threads:[~2002-02-26 20:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 19:57 schedule() Richard B. Johnson
2002-02-26 20:05 ` Jeff Garzik [this message]
2002-02-26 20:14   ` schedule() Richard B. Johnson
2002-02-27  0:56   ` schedule() Nigel Gamble
2002-02-27 15:29     ` schedule() Richard B. Johnson
2002-02-26 20:13 ` schedule() Davide Libenzi
2002-02-26 20:17   ` schedule() Richard B. Johnson
2002-02-26 20:19     ` schedule() Davide Libenzi
2002-02-26 20:47       ` schedule() Richard B. Johnson
2002-02-26 20:50         ` schedule() Davide Libenzi
2002-02-26 21:14       ` schedule() Richard B. Johnson
2002-02-26 22:37         ` schedule() Davide Libenzi

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=3C7BEA6F.97CB8AD4@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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

all inboxes | Powered by JetHome®