>
> And on FC5 I am using pthread_self but my problem isn't simply with
> pthread_self, it's with the scheduling.
maybe your kernel has a broken scheduler loadbalancing? you really
shouldn't have to do this manually. At all.
> On FC3 both threads run
> simultaneously in almost symmetric parallel. On FC5 one thread don't pick
> up and start until the previous one is done. On FC3, using getpid for the
> thread I could use set_afinity to force each thread to its own processor and
> with FC5 I can't; so I've got one idle processor all the time.
again you can use gettid() or pthread_self() in that call (but remember
it's a bitmask not a number); but really you shouldn't have to do this.
Try a kernel which has a non-broken load balancer?
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
