From: Mike Fedyk <mfedyk@matchmail.com>
To: Dan Chen <crimsun@email.unc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] #define yield() for 2.4 scheduler (anticipating O(1))
Date: Fri, 1 Mar 2002 10:58:25 -0800 [thread overview]
Message-ID: <20020301185825.GK2711@matchmail.com> (raw)
In-Reply-To: <20020301163237.GC16716@opeth.ath.cx>
In-Reply-To: <20020301163237.GC16716@opeth.ath.cx>
On Fri, Mar 01, 2002 at 11:32:37AM -0500, Dan Chen wrote:
> In response to Rik's post concerning a #define yield(), I've done a
> quick egrep over the 2.4.19-pre2 tree and modified as necessary. This is
> a strict search and replace. Thanks to Rik and Davide for assistance.
> Please correct me if I erred.
>
> --
> Dan Chen crimsun@email.unc.edu
> GPG key: www.unc.edu/~crimsun/pubkey.gpg.asc
> diff -uNr linux.orig/fs/buffer.c linux/fs/buffer.c
> --- linux.orig/fs/buffer.c Thu Feb 28 22:00:02 2002
> +++ linux/fs/buffer.c Fri Mar 1 10:29:52 2002
> @@ -735,9 +735,8 @@
> wakeup_bdflush();
> try_to_free_pages(zone, GFP_NOFS, 0);
> run_task_queue(&tq_disk);
> - current->policy |= SCHED_YIELD;
> __set_current_state(TASK_RUNNING);
> - schedule();
> + yield();
> }
>
> void init_buffer(struct buffer_head *bh, bh_end_io_t *handler, void *private)
is __set_current_state(TASK_RUNNING) compatible with the new scheduler?
next prev parent reply other threads:[~2002-03-01 18:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 16:32 [RFC][PATCH] #define yield() for 2.4 scheduler (anticipating O(1)) Dan Chen
2002-03-01 18:03 ` Davide Libenzi
2002-03-01 18:58 ` Mike Fedyk [this message]
2002-03-01 19:03 ` Dan Chen
2002-03-01 21:18 ` Bongani Hlope
2002-03-01 21:13 ` Rik van Riel
2002-03-02 17:38 ` Dan Chen
2002-03-01 22:28 ` Ken Brownfield
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=20020301185825.GK2711@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=crimsun@email.unc.edu \
--cc=linux-kernel@vger.kernel.org \
/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.