From: Sujit K M <sjt.kar@gmail.com>
To: Primiano Tucci <p.tucci@gmail.com>
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Re: Strange behavior of pthread_setaffinity_np
Date: Mon, 19 Apr 2010 17:31:59 +0530 [thread overview]
Message-ID: <y2y921ca19c1004190501xdd8506a3j3f4337caf272c55c@mail.gmail.com> (raw)
In-Reply-To: <w2n921ca19c1004190501n36c7f10ch484cda701e261ee9@mail.gmail.com>
On Mon, Apr 19, 2010 at 5:31 PM, Sujit K M <sjt.kar@gmail.com> wrote:
> On Mon, Apr 19, 2010 at 5:21 PM, Primiano Tucci <p.tucci@gmail.com> wrote:
>> Hi Sujit,
>> thanks for your reply, but I have not completely understood your point.
>> Does the kernel make (from the thread viewpoint) differences between
>> Cores of a Processor, or multiple processors?
>
> Yes, It certainly does for Kernel Level Routines. But on User level
> Applications,
> These Might not be the case.
>
>> In my previous speak I generally used the term CPU #0 and #1 to refer
>> to two different cores of a same Processor (a quad core Q9550).
>
> What I had in mind for Quad was Four Cores per Processors.
>
>> Do you mean I need a different API to sett affinity on a per-core
>> basis rather than a per-processor basis? It sound strange to me, as in
>> my little knowledge Cores are viewed, by the system, as different
>> processor, just as in the case of a regular Multi Processor system.
>
> I donot think these API's Have been developed.
>
--
-- Sujit K M
blog(http://kmsujit.blogspot.com/)
next prev parent reply other threads:[~2010-04-19 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 9:45 Strange behavior of pthread_setaffinity_np Primiano Tucci
2010-04-19 11:07 ` Sujit K M
2010-04-19 11:51 ` Primiano Tucci
[not found] ` <w2n921ca19c1004190501n36c7f10ch484cda701e261ee9@mail.gmail.com>
2010-04-19 12:01 ` Sujit K M [this message]
2010-04-19 20:18 ` Primiano Tucci
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=y2y921ca19c1004190501xdd8506a3j3f4337caf272c55c@mail.gmail.com \
--to=sjt.kar@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=p.tucci@gmail.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).