From: "J . A . Magallon" <jamagallon@able.es>
To: Ying Chen <yingchenb@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: threads
Date: Wed, 7 Mar 2001 01:07:34 +0100 [thread overview]
Message-ID: <20010307010734.C1132@werewolf.able.es> (raw)
In-Reply-To: <F41oVQAiEGKROptzzpY000014a6@hotmail.com>
In-Reply-To: <F41oVQAiEGKROptzzpY000014a6@hotmail.com>; from yingchenb@hotmail.com on Wed, Mar 07, 2001 at 00:55:55 +0100
On 03.07 Ying Chen wrote:
> 2. We ran multi-threaded application using Linux pthread library on 2-way
> SMP and UP intel platforms (with both 2.2 and 2.4 kernels). We see
> significant increase in context switching when moving from UP to SMP, and
> high CPU usage with no performance gain in turns of actual work being done
> when moving to SMP, despite the fact the benchmark we are running is
> CPU-bound. The kernel profiler indicates that the a lot of kernel CPU ticks
> went to scheduling and signaling overheads. Has anyone seen something like
> this before with pthread applications running on SMP platforms? Any
> suggestions or pointers on this subject?
>
Too much contention ? How frequently do you create and destroy threads ?
How much frequently do they access shared-writable-data ?
How do you protect them ?
It seems like your system spents more time creating and killing threads
that doing real work.
--
J.A. Magallon $> cd pub
mailto:jamagallon@able.es $> more beer
Linux werewolf 2.4.2-ac13 #3 SMP Wed Mar 7 00:09:17 CET 2001 i686
next prev parent reply other threads:[~2001-03-07 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 23:55 Ying Chen
2001-03-07 0:07 ` J . A . Magallon [this message]
2001-03-07 0:40 ` your mail Don Dugger
-- strict thread matches above, loose matches on Subject: below --
2000-11-10 15:03 threads M.Kiran Babu
2000-11-10 15:39 ` threads Matti Aarnio
2000-11-10 16:05 ` threads Reto Baettig
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=20010307010734.C1132@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=yingchenb@hotmail.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;
as well as URLs for NNTP newsgroup(s).