Date: Fri, 16 Feb 2007 14:04:05 -0500 (EST) From: Daniel Eischen <deischen@freebsd.org> To: John Giacomoni <John.Giacomoni@colorado.edu> Cc: freebsd-hackers@freebsd.org, Julian Elischer <jelischer@ironport.com> Subject: Re: pin/bind a pthread to a processor? (take 2) Message-ID: <Pine.GSO.4.64.0702161355160.20040@sea.ntplx.net> In-Reply-To: <1959ECB1-61D4-4034-BB10-83D68DA01B13@colorado.edu> References: <368841.53689.qm@web32903.mail.mud.yahoo.com> <45CD31D3.8040106@ironport.com> <Pine.GSO.4.64.0702092348170.12150@sea.ntplx.net> <1959ECB1-61D4-4034-BB10-83D68DA01B13@colorado.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
What you are trying to do is real-time work. You will need to place your thread(s) or process in the real-time class or priority range and modify the scheduler(s) if necessary to support RT. I'm not familiar with the schedulers, but I suspect most of your work should be spent on getting one of the schedulers (whichever can more easily support it) to operate correctly for RT threads and processes. RT is something that I found Solaris is pretty good at, at least with later versions of Solaris. You might investigate that if you can't get FreeBSD to operate efficiently/correctly for RT processing. We have been using Solaris for real-time simulation for many years now. I would love to be able to use FreeBSD as well, especially because we can embed it a lot easier than Solaris, but I don't think it's quite there yet. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0702161355160.20040>