From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sujit K M Subject: Re: Strange behavior of pthread_setaffinity_np Date: Mon, 19 Apr 2010 17:31:59 +0530 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: RT To: Primiano Tucci Return-path: Received: from mail-qy0-f182.google.com ([209.85.221.182]:64970 "EHLO mail-qy0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753866Ab0DSMCD (ORCPT ); Mon, 19 Apr 2010 08:02:03 -0400 Received: by qyk12 with SMTP id 12so5144860qyk.21 for ; Mon, 19 Apr 2010 05:02:01 -0700 (PDT) In-Reply-To: Sender: linux-rt-users-owner@vger.kernel.org List-ID: On Mon, Apr 19, 2010 at 5:31 PM, Sujit K M wrote: > On Mon, Apr 19, 2010 at 5:21 PM, Primiano Tucci 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/)