From: David Mansfield <lkml@dm.ultramaster.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Mike Galbraith <mikeg@wen-online.de>, Jens Axboe <axboe@suse.de>,
MOLNAR Ingo <mingo@chiara.elte.hu>,
Rik van Riel <H.H.vanRiel@phys.uu.nl>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [BUG] /proc/<pid>/stat access stalls badly for swapping process,2.4.0-test10
Date: Fri, 10 Nov 2000 16:42:46 -0500 [thread overview]
Message-ID: <3A0C6BD6.A8F73950@dm.ultramaster.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10011091005390.1909-100000@penguin.transmeta.com>
Linus Torvalds wrote:
...
>
> And it has everything to do with the fact that the way Linux semaphores
> are implemented, a non-blocking process has a HUGE advantage over a
> blocking one. Linux kernel semaphores are extreme unfair in that way.
>
...
> The original running process comes back faulting again, finds the
> semaphore still unlocked (the "ps" process is awake but has not gotten to
> run yet), gets the semaphore, and falls asleep on the IO for the next
> page.
>
> The "ps" process actually gets to run now, but it's a bit late. The
> semaphore is locked again.
>
> Repeat until luck breaks the bad circle.
>
But doesn't __down have a fast path coded in assembly? In other words,
it only hits your patched code if there is already contention, which
there isn't in this case, and therefore the bug...?
David Mansfield
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-10 21:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.Linu.4.10.10011091452270.747-100000@mikeg.weiden.de>
2000-11-09 18:31 ` [BUG] /proc/<pid>/stat access stalls badly for swapping process, 2.4.0-test10 Linus Torvalds
2000-11-10 7:34 ` Mike Galbraith
2000-11-10 10:47 ` Mike Galbraith
2000-11-10 17:07 ` Linus Torvalds
2000-11-10 21:42 ` David Mansfield [this message]
2000-11-11 6:20 ` [BUG] /proc/<pid>/stat access stalls badly for swapping process,2.4.0-test10 Linus Torvalds
2000-11-01 18:38 [BUG] /proc/<pid>/stat access stalls badly for swapping process, 2.4.0-test10 David Mansfield
2000-11-01 18:48 ` Rik van Riel
2000-11-02 7:19 ` Mike Galbraith
2000-11-02 21:59 ` Val Henson
2000-11-03 1:37 ` Jens Axboe
2000-11-03 5:56 ` Mike Galbraith
2000-11-03 15:45 ` Mike Galbraith
2000-11-03 19:38 ` Jens Axboe
2000-11-04 5:43 ` Mike Galbraith
2000-11-02 8:40 ` Christoph Rohland
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=3A0C6BD6.A8F73950@dm.ultramaster.com \
--to=lkml@dm.ultramaster.com \
--cc=H.H.vanRiel@phys.uu.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
--cc=mingo@chiara.elte.hu \
--cc=torvalds@transmeta.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