[openbeosnetteam] Re: Dragonfly or FreeBSD nestack? was Re: Mailing lists and network team questions
- From: Waldemar Kornewald <wkornew@xxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Sat, 18 Mar 2006 21:14:25 +0100
Axel Dörfler wrote:
CPU affinity just means that the scheduler *tries* to keep a thread to
a certain CPU - if the other CPU has free slots it won't hesitate to
take a thread away from the other CPU, though - ie. you can't use this
for anything, it's just faster, because the CPU's cache is likely to be
trashed less often :)
On some website I even read that it can mean that a thread is restricted
to a subset of the available CPUs (CPUs 1, 4, and 9, for example)...very
strange.
As I said, several times already now: you can easily implement
serializing tokens using mutexes. No performance hit at all, and yet,
you can't run into the deadlock problem.
I don't really know how to implement them with mutexes. I.e.: whenever I
block on a mutex all other mutexes held by the current thread would have
to allow for other threads to get the mutexes or am I on the totally
wrong track, here? To me, mutexes look like special semaphores that can
protect against priority inversion. Could you please clarify? I'm just
curious.
Anyway, I won't do this for R1. There are more important things, ATM.
For R2 we should list all tools we might need...tokens would be very
interesting and I'd like to get my hands on this.
Bye,
Waldemar
Other related posts: