From: Christoph Rohland <cr@sap.com>
To: David Mansfield <lkml@dm.ultramaster.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] semaphore fairness patch against test11-pre6
Date: 18 Nov 2000 10:45:07 +0100 [thread overview]
Message-ID: <m3bsvdd36k.fsf@linux.local> (raw)
In-Reply-To: <3A15D4F5.B39D61BD@dm.ultramaster.com>
In-Reply-To: David Mansfield's message of "Fri, 17 Nov 2000 20:01:41 -0500"
Hi David,
David Mansfield <lkml@dm.ultramaster.com> writes:
> If you can find the time to check this out more completely, I recommend
> it, because it seems like a great improvement to be able to accurately
> see vmstat numbers in times of system load. I hope the other side
> effects are beneficial as well :-)
I wanted to point out that there may be some performance impacts by
this: We had exactly the new behaviour on SYSV semaphores. It led to
very bad behaviour in high load situations since for high frequency,
short critical paths this led to very high context switch rates
instead of using the available time slice for the program.
We changed the behaviour of SYSV semaphores to the current kernel sem
behaviour and never had problems with that change.
I still think that your change is right since this is kernel space and
you do not have the notion of a time slice.
Christoph
-
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-18 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-18 1:01 [PATCH] semaphore fairness patch against test11-pre6 David Mansfield
2000-11-18 9:45 ` Christoph Rohland [this message]
2000-11-19 1:12 ` Andrew Morton
2000-11-19 1:47 ` Linus Torvalds
2000-11-19 12:51 ` Andrew Morton
2000-11-19 18:46 ` Linus Torvalds
2000-11-20 13:39 ` Andrew Morton
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=m3bsvdd36k.fsf@linux.local \
--to=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dm.ultramaster.com \
--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