Re: Binding a thread (or specific process) to a designated CPU

On 8/22/05, Brian D. McGrew <[email protected]> wrote:
> Good morning,
> 
> Using FC3 or FC4 with the 2.6.9 or later kernel, we're looking for a way
> to bind a thread (or an entire process) to a designated CPU.  We're

       #include <sched.h>

       int sched_setaffinity(pid_t pid, unsigned int len, unsigned long *mask);
       int sched_getaffinity(pid_t pid, unsigned int len, unsigned long *mask);


-- 
Jesper Juhl <[email protected]>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Binding a thread (or specific process) to a designated CPU
    • From: "Brian D. McGrew" <[email protected]>

• Prev by Date: Re: [linux-usb-devel] [PATCH] hiddev: output reports are dropped when HIDIOCSREPORT is called in short succession
• Next by Date: Re: Binding a thread (or specific process) to a designated CPU
• Previous by thread: Binding a thread (or specific process) to a designated CPU
• Next by thread: Re: Binding a thread (or specific process) to a designated CPU
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]