Re: Strange behavior of pthread_setaffinity_np

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Apr 19, 2010 at 5:31 PM, Sujit K M <sjt.kar@xxxxxxxxx> wrote:
> On Mon, Apr 19, 2010 at 5:21 PM, Primiano Tucci <p.tucci@xxxxxxxxx> 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/)
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux