Re: server: Use kernel support for process affinity when available (try 2)

[Alexandre Julliard]

Juan Lang <juan.lang(a)gmail.com> writes:
> Is this better?  This trades a single call to sched_getaffinity per
> process to one every time the process affinity is queried.  This seems
> safer, since a non-Wine process can also change a process's affinity,
> but it can have higher overhead.

Yes, that's better. But AFAICT sched_get/setaffinity applies to a
single thread, not to the whole process.

-- 
Alexandre Julliard
julliard(a)winehq.org

server: Use kernel support for process affinity when available (try 2)

[Darragh Bailey]

On Wed, Jan 28, 2009 at 02:46:00PM +0100, Alexandre Julliard wrote:
> Juan Lang <juan.lang(a)gmail.com> writes:
> > Is this better?  This trades a single call to sched_getaffinity per
> > process to one every time the process affinity is queried.  This seems
> > safer, since a non-Wine process can also change a process's affinity,
> > but it can have higher overhead.
>
> Yes, that's better. But AFAICT sched_get/setaffinity applies to a
> single thread, not to the whole process.

I believe that's only where you provide the thread id instead of the
process id.

-- 
Darragh

"Nothing is foolproof to a sufficiently talented fool."