From: Hil <ubuntu@comcast.net>
To: kernel-janitors@vger.kernel.org
Subject: fix yield
Date: Mon, 11 Sep 2006 21:52:18 +0000 [thread overview]
Message-ID: <1158011538.9376.4.camel@localhost> (raw)
I am interested in fixing the yield() at
http://marc.theaimsgroup.com/?l=kernel-janitor-discuss&m\x107395278319388&w=2
Has this task been assigned? I will take over if no one has done it. I
just got kernel 2.6.18.rc6 and still found yield under drivers. Please
give me some hints of how to fix the yield. When do I replace yield()
with cond_resched(), schedule() or even schedule_timeout()? I will look
into these functions.
Hil
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Kernel-janitor-discuss mailing list
Kernel-janitor-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kernel-janitor-discuss
reply other threads:[~2006-09-11 21:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1158011538.9376.4.camel@localhost \
--to=ubuntu@comcast.net \
--cc=kernel-janitors@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.