LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "J.A. Magallón" <jamagallon@ono.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Brian McGrew <brian@visionpro.com>,
	linux-kernel@vger.kernel.org, fedora-users@rdhat.com
Subject: Re: Threading...
Date: Sat, 20 Jan 2007 02:18:45 +0100	[thread overview]
Message-ID: <20070120021845.02b4f4fc@werewolf-wl> (raw)
In-Reply-To: <1169232941.3055.555.camel@laptopd505.fenrus.org>

On Fri, 19 Jan 2007 19:55:41 +0100, Arjan van de Ven <arjan@infradead.org> wrote:

> On Fri, 2007-01-19 at 10:43 -0800, Brian McGrew wrote:
> > I have a very interesting question about something that we're seeing
> > happening with threading between Fedora Core 3 and Fedora Core 5.  Running
> > on Dell PowerEdge 1800 Hardware with a Xeon processor with hyper-threading
> > turned on.  Both systems are using a 2.6.16.16 kernel (MVP al la special).
> > 
> > We have a multithreaded application that starts two worker threads.  On
> > Fedora Core 3 both of these we use getpid() to get the PID of the thread and
> > then use set_afinity to assign each thread to it's own CPU.  Both threads
> > run almost symmetrically even on their given CPU watching the system
> > monitor.
> 
> this is odd; even in FC3 getpid() is supposed to return the process ID
> not the thread ID
> 
> > What am I missing?  What do I need to do in FC5 or the kernel or the
> > threading library to get my threads to run in symmetric parallel again???
> 

One thing to try. In linux, pthread_setconcurrency never did nothing
(it _really_ did in IRIX...). Can you try that ? Perhaps FC5 has implemented
some kind of scheduling policy like that on irix (everything stays on the
same CPU until it starts to suck cycles, unless you use setconcurrency).

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2007.1 (Cooker) for i586
Linux 2.6.19-jam04 (gcc 4.1.2 20061110 (prerelease) (4.1.2-0.20061110.2mdv2007.1)) #0 SMP PREEMPT

      parent reply	other threads:[~2007-01-20  1:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 18:43 Threading Brian McGrew
2007-01-19 18:55 ` Threading Arjan van de Ven
2007-01-19 19:01   ` Threading Brian McGrew
2007-01-19 19:23     ` Threading Arjan van de Ven
2007-01-19 21:26     ` Threading Bill Davidsen
2007-01-20  1:18   ` J.A. Magallón [this message]

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=20070120021845.02b4f4fc@werewolf-wl \
    --to=jamagallon@ono.com \
    --cc=arjan@infradead.org \
    --cc=brian@visionpro.com \
    --cc=fedora-users@rdhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Threading...' \
    /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

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).