From: Sasha Pachev <sasha@mysql.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Mike Kravetz <mkravetz@sequent.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Strange thread behaviour on 8-way x86 machine
Date: Fri, 6 Jul 2001 14:35:33 -0600 [thread overview]
Message-ID: <01070614353314.17811@mysql> (raw)
In-Reply-To: <Pine.LNX.4.33L.0107061624370.17825-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0107061624370.17825-100000@duckman.distro.conectiva>
On Friday 06 July 2001 13:24, Rik van Riel wrote:
> On Fri, 6 Jul 2001, Sasha Pachev wrote:
>
> > Upon further investigation and testing, it turned out that the kernel was
not
> > at fault - the problem was high mutex contention, which caused frequent
> > context switches, and the idle CPU was apparently from the scheduler
waiting
> > for the original CPU to become available too often.
> >
> > On a side note, it would be nice if a process could communicate
> > to the kernel that it would rather run on the first available
> > CPU than wait for the perfect one to become available.
>
> The kernel already does this.
Thanks for the info. Would you mind proving a one line pointer on how to tell
this to the kernel?
--
MySQL Development Team
For technical support contracts, visit https://order.mysql.com/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sasha Pachev <sasha@mysql.com>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA
<___/
next prev parent reply other threads:[~2001-07-06 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 18:25 Strange thread behaviour on 8-way x86 machine Sasha Pachev
2001-07-03 18:51 ` Mike Kravetz
2001-07-06 18:45 ` Sasha Pachev
2001-07-06 19:24 ` Rik van Riel
2001-07-06 20:35 ` Sasha Pachev [this message]
2001-07-06 20:41 ` Rik van Riel
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=01070614353314.17811@mysql \
--to=sasha@mysql.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkravetz@sequent.com \
--cc=riel@conectiva.com.br \
/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;
as well as URLs for NNTP newsgroup(s).