Date: Thu, 12 Apr 2007 15:04:29 +0200 From: Ivan Voras <ivoras@fer.hr> To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no> Cc: Randall Stewart <rrs@cisco.com>, freebsd-current@freebsd.org Subject: Re: CPU utilization Message-ID: <461E2E5D.1090409@fer.hr> In-Reply-To: <86slb5ycmd.fsf@dwp.des.no> References: <461E0078.3050001@cisco.com> <20070412114344.G64803@fledge.watson.org> <461E1D4E.3090806@cisco.com> <evl95h$969$1@sea.gmane.org> <461E2C07.5000503@cisco.com> <86slb5ycmd.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig043FBD150EA591F0923322AC Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Dag-Erling Sm=C3=B8rgrav wrote: > Randall Stewart <rrs@cisco.com> writes: >> Sure.. dumb question though.. whats the magic cookie to pin >> something on a cpu.. is it a system call or is there a "shell" tool >> that will do it? >=20 > Neither. There is a kernel function to tie a thread to a CPU, but it > is not exported to userland. I was thinking about the kernel part, but now, thinking more, it's=20 probably very non-trivial to do. I though that using sched_bind() could=20 do it, but this only works if there's a specific thread created for some = task - I don't know how can something like 'a network stack', which=20 consists of myriad of callbacks and asynchrounsly called functions, be=20 pinned. Sorry for the noise. :) --------------enig043FBD150EA591F0923322AC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGHi5dldnAQVacBcgRAriBAJ9qm9zRknu2WgWlDNKU/o9qptSclQCgwORf h5hAEXOxNKFvsmHL8qpVdz8= =oaL+ -----END PGP SIGNATURE----- --------------enig043FBD150EA591F0923322AC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?461E2E5D.1090409>