Date: Mon, 28 Jan 2019 12:37:44 +0100 From: =?UTF-8?Q?Christian_St=c3=a6rk?= <xi@borderworlds.dk> To: Poul-Henning Kamp <phk@phk.freebsd.dk>, Babak Farrokhi <farrokhi@FreeBSD.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Mark Saad <nonesuch@longcount.org> Subject: Re: CPU Isolation Message-ID: <011a4a81-1cca-d97e-a355-9f2e8ff8b5c6@borderworlds.dk> In-Reply-To: <64099.1548664473@critter.freebsd.dk> References: <CAMXt9NbKwZAwv%2BWJ4yqmeMFmX38n=qjUqJSq4kOq2qdNSVEhHg@mail.gmail.com> <AC6FACC4-2403-41B7-B7E6-738A692929A2@FreeBSD.org> <64099.1548664473@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/28/19 9:34 AM, Poul-Henning Kamp wrote: > -------- > In message <AC6FACC4-2403-41B7-B7E6-738A692929A2@FreeBSD.org>, "Babak Farrokhi" writes: > >> AFAIK there is no way to do it pre-boot. To do the isolation post-boot your >> best bet is cpuset(1) (with which I could not totally isolate cpu cores >> as dedicated application cores). > The trick is to move /sbin/init to /sbin/init.real and create a > /sbin/init shell script which cpuset's PID=1 then exec's /sbin/init.real > > Be aware that the surroundings of that shell script are very sparse. > Or maybe set "init_path" in loader.conf to point to the init wrapper and then keep /sbin/init unchanged. Then subsequent system updates would not break the setup. Best regards Christian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?011a4a81-1cca-d97e-a355-9f2e8ff8b5c6>