getting curious about multi-core tasking

Steve Volumetric volumetricsteve at
Sun Dec 18 17:32:41 UTC 2016


thanks for your replies, of all solutions offered, it looks like isolcpus
gets me the closest.

I read up on isolcpus and it seems like it will partition off cores away
from automatic spawing of userland threads, which is...close enough to what
i want.  i did read, however that kworker threads will continue to spawn
across all cores.  this makes me wonder how it might work in my case

if java instances are running on 4 cores, and kworkers can spawn anywhere,
isnt all the work being done in java eventually going to end up in a
kworker..and therefore just running anywhere?

maybe ill just have to do some testing and see what happens

On Dec 17, 2016 9:23 AM, "Predrag Ivanovic" <predivan at> wrote:

> On Fri, 16 Dec 2016 17:33:23 -0500
> Steve Volumetric wrote:
> >Yes, I should have used that phrasing in my question, and I see all that
> >(I've already emailed myself a few of the links you provided) thanks for
> >those anyway.
> >
> >My concern/question is more...can I get crux to do that to itself on
> >startup...or really, maybe a better way of describing what I would like to
> >do is have 4 of my 6 cores untouched by whatever automatically schedules
> >jobs so I (and only I) can manually set affinity to jobs on those free
> >cores as I choose.
> >
> Check out Fedora's Tuna/tuned [1][2], they might do what you want.
> [1]
> [2]
> _______________________________________________
> CRUX mailing list
> CRUX at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the CRUX mailing list