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. On Fri, Dec 16, 2016 at 5:30 PM, Louis Santillan <lpsantil@gmail.com> wrote:

The word you're looking for is CPU Affinity. See [0][1][2][3].

[0] https://sourceforge.net/projects/schedutils/ [1] https://www.cyberciti.biz/tips/setting-processor- affinity-certain-task-or-process.html [2] http://www.glennklockwood.com/hpc-howtos/process-affinity.html [3] http://man7.org/linux/man-pages/man2/sched_setaffinity.2.html

On Fri, Dec 16, 2016 at 2:09 PM, Steve Volumetric <volumetricsteve@gmail.com> wrote:

...

Hey everyone,

I'm about to set up a server (minecraft, sorry) and what I'd like to do is ensure consistency of service, even if it's at the cost of a performance hit.

My thinking is, if I can get crux to boot up...some way, maybe it could launch and lock all things brought up at system-startup-time to say...core 0. As far as many services would be concerned, they'd be on a single core system.

With my other 5 cores, I'd like to designate each core to a particular world, and this is done fairly easily, but my real question is up above.

Can I get crux to relegate its services to a single core consistently? If not one, maybe two?

Thanks

_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux

On Sat, Dec 17, 2016, 00:33 Steve Volumetric <volumetricsteve@gmail.com> wrote:

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.

Isn't isolcpus boot parameter what you want? kernel.org/doc/Documentation/kernel-parameters.txt

ALCON, 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 though. 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@mts.rs> 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]https://fedorahosted.org/tuned [2]https://fedorahosted.org/tuna _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux