linux-kernel - Re: Thread Affinity structure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.1102041412170.6690@router.home>
Date:	Fri, 4 Feb 2011 14:13:12 -0600 (CST)
From:	Christoph Lameter <cl@...ux.com>
To:	Sri Ram Vemulpali <sri.ram.gmu06@...il.com>
cc:	Kernel-newbies <kernelnewbies@...linux.org>,
	linux-kernel-mail <linux-kernel@...r.kernel.org>
Subject: Re: Thread Affinity structure

On Fri, 4 Feb 2011, Sri Ram Vemulpali wrote:

> Hi Christoph,
>
>   Thanks for response. Can you please explain in little bit elaborate
> what do you mean
>
>  "The value returned  from a call to gettid(2) can be passed in the argument
>  pid.  Specifying pid as 0 will set the attribute for the calling thread,
>  and passing the value returned from a call to getpid(2) will set the
>  attribute for the main thread of the thread group."
>
> To whom I should pass the id. I did not understood.

The passage was from the man page that you get by typing

man sched_setaffinity


You pass the id as a parameter to sched_setaffinity.