Date: Thu, 22 Feb 2024 16:20:23 +0100 From: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> To: freebsd-hackers@freebsd.org Subject: Re: jails and CPU pinning Message-ID: <96601c87-ad15-4afe-b949-31ad2670246f@plan-b.pwste.edu.pl> In-Reply-To: <slrnuteih8.1ebh.pmc@disp.intra.daemon.contact> References: <bc619b88-945c-4c6b-ba99-4de1a361caab@plan-b.pwste.edu.pl> <slrnuteih8.1ebh.pmc@disp.intra.daemon.contact>
next in thread | previous in thread | raw e-mail | index | archive | help
W dniu 22.02.2024 o 14:20, Peter 'PMc' Much pisze: > On 2024-02-13, Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> wrote: >> Dear Knowledgeable Hackers, >> >> is CPU pinning supposed to work from inside the jail if the jail CPU set >> is full? >> From my observations processes inside the jails don't walk over >> CPUs(?!) and can be pinned to specific CPUs neither from the host nor >> from the jail. Is this expected behavior? > root@edge:~ # jexec admn > root@admn:/ # cpuset -g -p $$ > pid 54831 mask: 6, 7, 8, 9 > pid 54831 domain policy: prefer mask: 0 > root@admn:/ # cpuset -l 9 bash > [root@admn /]# cpuset -g -p $$ > pid 55156 mask: 9 > pid 55156 domain policy: first-touch mask: 0, 1 > > So what exactly is Your problem? > Thanks for the reply, Peter. There is no problem anymore. I was just using the wrong tools to investigate. In jails, everything involving CPU affinity seems to be working as intended. Please let me apologize for the noise on the mailing list. -- Marek Zarychta
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96601c87-ad15-4afe-b949-31ad2670246f>