SCIENTIFIC-LINUX-USERS Archives

April 2012

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stephen John Smoogen <[log in to unmask]>
Reply To:
Stephen John Smoogen <[log in to unmask]>
Date:
Thu, 5 Apr 2012 12:18:38 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
On 5 April 2012 10:47, Wil Irwin <[log in to unmask]> wrote:
> Hi-
>
> I am totally stumped and at a complete loss on this one.
>
> In an 'old school' manner (a.k.a poor man's grid engine), it is a common
> practice (at least for me) to open multiple terminal windows on a
> mullti-core machine. Submitting a job in each terminal window will send it
> to a core which is not being used. On this particular set of machines I have
> been doing this for about 2 years.

To be honest I have no idea why it worked before. Setting a process to
a certain core takes definitive coding to say "x will have affinity to
CPU y" or using a program like taskset to set the affinity.

I would try the following:
1) man taskset
2) see if taskset works on your system.

Then see if it works. If it doesn't then I would assume that the CPU
or some other hardware in the box is having issues and not allowing
processes on the other cores for some reason.


-- 
Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Years ago my mother used to say to me,... Elwood, you must be oh
so smart or oh so pleasant. Well, for years I was smart. I
recommend pleasant. You may quote me."  —James Stewart as Elwood P. Dowd

ATOM RSS1 RSS2