hi, thanks for your input, however it does not help really
linked doc? I've thumb trough it before.
let me rephrase my question - how do I put users, their
whole session from the moment they login into a cgroup cpuset?
and I don't want to use libcgroup (as it not recommended
anyway) but have systemd managed it.
thanks
On 29/07/14 20:38, Michael Cronenworth wrote:
On 07/29/2014 09:11 AM, lejeczek wrote:
I thought I could easily (as easily as I could do that
with libcgroup)
permanently restric a user to a specific cpu core.
I thought it would be CPUAffinity responsible for it
either in
systemd-user-sessions or(and) in systemd-logind
but it does not work,
is it possible to have user(s) sessions permanently
restricted in this way? so
his/her processes would be executed only on given core?
if yes then how would you do this? please shed some light
You should find everything you need to know on this page.
https://www.kernel.org/doc/Documentation/cgroups/cpusets.txt
The basics of it are broken down like this:
1. Create a new cpuset
2. Set cpuset settings (single cpu, etc.)
3. Start task using the new cpuset
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
