From: Yuly Finkelberg <liquidicecube@gmail.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scheduler: Spinning until tasks are STOPPED
Date: Sat, 7 May 2005 13:36:21 -0400 [thread overview]
Message-ID: <92df3175050507103621a88554@mail.gmail.com> (raw)
In-Reply-To: <427C6A5C.6090900@yahoo.com.au>
Nick,
> You're doing this in the *kernel*? It sounds like it should be done
> in userspace or done a different way (ie. not with 50 tasks).
These are tasks that are running in the kernel on behalf of a new system call.
> And using signals and spinning on yield for synchronisation and
> process control in the kernel like this is fairly crazy.
The problem appears to be not with the process that is
spinning/yielding, but rather the one process which gets stuck. It is
charged almost all the system time. I agree that it's not pretty
though...
> Can't you use a semaphore or something?
There is noone to call up() when a process is actually stopped.
If you have any ideas as to what can be happening or a better way to
accomplish this (in the kernel), I'd appreciate hearing it.
next prev parent reply other threads:[~2005-05-07 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 6:31 Yuly Finkelberg
2005-05-07 7:12 ` Nick Piggin
2005-05-07 17:36 ` Yuly Finkelberg [this message]
2005-05-08 4:00 ` Nick Piggin
2005-05-09 0:10 ` Yuly Finkelberg
[not found] ` <92df317505050817071d852623@mail.gmail.com>
2005-05-09 6:05 ` Nick Piggin
[not found] <41r8S-6Y0-13@gated-at.bofh.it>
[not found] ` <41rLz-7zl-5@gated-at.bofh.it>
[not found] ` <41BrD-79c-29@gated-at.bofh.it>
2005-05-07 22:38 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
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=92df3175050507103621a88554@mail.gmail.com \
--to=liquidicecube@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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
Powered by JetHome