From: Sean Hunter <sean@dev.sportingbet.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Rik van Riel <riel@conectiva.com.br>,
Bill Davidsen <davidsen@tmr.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-preX: What we really need: -AA patches finally in the tree
Date: Fri, 1 Mar 2002 10:36:00 +0000 [thread overview]
Message-ID: <20020301103600.D7765@dev.sportingbet.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0203010009510.2801-100000@imladris.surriel.com> <Pine.LNX.4.44.0202281942420.939-100000@blue1.dev.mcafeelabs.com>
In-Reply-To: <Pine.LNX.4.44.0202281942420.939-100000@blue1.dev.mcafeelabs.com>; from davidel@xmailserver.org on Thu, Feb 28, 2002 at 07:43:57PM -0800
Excuse my stupidity, but would a patch that just adds Davide's macro and
changes all instances of
current->policy |= SCHED_YIELD;
schedule();
to yield() be acceptable? Is there more involved than that, because I am
perfectly happy to create and submit such a patch.
...or am I just being dumb?
Sean
On Thu, Feb 28, 2002 at 07:43:57PM -0800, Davide Libenzi wrote:
> On Fri, 1 Mar 2002, Rik van Riel wrote:
>
> > Not at all. The yield() function would just be a define to
> > the code which no longer works with the new scheduler, ie:
> >
> > #define yield() \
> > current->policy |= SCHED_YIELD; \
> > schedule();
>
> or better :
>
> #define yield() \
> do { \
> current->policy |= SCHED_YIELD; \
> schedule(); \
> } while (0)
>
>
>
> - Davide
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-03-01 10:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 0:35 2.4.19-preX: What we really need: -AA patches finally in the tree Dieter Nützel
2002-02-26 1:02 ` Ken Brownfield
2002-02-26 1:13 ` Andrew Morton
2002-02-26 7:20 ` Jens Axboe
2002-02-26 1:39 ` Alan Cox
2002-02-26 1:15 ` Shawn Starr
2002-02-26 1:32 ` Martin J. Bligh
2002-02-24 5:44 ` Daniel Phillips
2002-02-26 4:33 ` Martin J. Bligh
2002-02-26 11:42 ` Rik van Riel
2002-02-26 1:40 ` Rik van Riel
2002-02-26 1:49 ` Martin J. Bligh
2002-02-26 1:51 ` Alan Cox
2002-02-26 8:36 ` Christoph Rohland
2002-02-26 7:07 ` Christoph Hellwig
2002-02-26 16:21 ` Mike Fedyk
2002-02-26 16:53 ` Christoph Hellwig
2002-02-28 22:45 ` Bill Davidsen
2002-02-28 23:04 ` Rik van Riel
2002-03-01 1:04 ` 2.4.19-preX: What we really need: -AA patches finally in the Alan Cox
2002-03-01 1:14 ` Rik van Riel
2002-03-01 3:02 ` 2.4.19-preX: What we really need: -AA patches finally in the tree Bill Davidsen
2002-03-01 3:13 ` Rik van Riel
2002-03-01 3:43 ` Davide Libenzi
2002-03-01 10:36 ` Sean Hunter [this message]
2002-03-01 17:13 ` Davide Libenzi
2002-03-01 6:29 ` Olivier Galibert
2002-03-01 16:28 ` Dan Chen
-- strict thread matches above, loose matches on Subject: below --
2002-03-01 6:41 dart
2002-03-05 21:49 ` Bill Davidsen
2002-03-06 1:05 ` Alan Cox
2002-03-06 1:45 ` James M.
2002-03-06 16:50 ` Ken Brownfield
2002-03-07 10:11 ` Leonid Mamtchenkov
2002-03-06 23:34 ` Yven Leist
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=20020301103600.D7765@dev.sportingbet.com \
--to=sean@dev.sportingbet.com \
--cc=davidel@xmailserver.org \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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