miguelperes / custom-malloc Goto Github PK

What alternatives could be used to the pthreads mutex, and how exactly is this pthread_mutex_unlock achieves its end goal.

I'm aware of the Unix method of Mutex, another solution could be to have a heap allocated to each CPU Core, which would be ideal if each core was assigned to a different task.

Would hyper-threading cause any unforeseen issues in such an implementation though I wonder?

I'm using your code for a project and it seems like the first chunk is marked as not available, which causes the first allocation request to fail.

Should head->available = 0; on line 189 be head->available = 1; ?

Thanks!