Date: Mon, 28 Jan 2019 08:34:33 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "Babak Farrokhi" <farrokhi@FreeBSD.org> Cc: "Mark Saad" <nonesuch@longcount.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: CPU Isolation Message-ID: <64099.1548664473@critter.freebsd.dk> In-Reply-To: <AC6FACC4-2403-41B7-B7E6-738A692929A2@FreeBSD.org> References: <CAMXt9NbKwZAwv%2BWJ4yqmeMFmX38n=qjUqJSq4kOq2qdNSVEhHg@mail.gmail.com> <AC6FACC4-2403-41B7-B7E6-738A692929A2@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
-------- 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. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?64099.1548664473>