On 14.04.2013 12:08, Gilles Chanteperdrix wrote:
> PI mutexes are not sufficient to make malloc deterministic. I guess if
> you are looking for a deterministic malloc, you should have a look at TLSF.
Yup, I know that malloc from glibc is a complicated beast and should
be probably not used at all during hard realtime operation.
Right now my biggest problem is the possibility of priority inversion.
My time constraints are in the 20 - 50 ms range and I hope the malloc
itself - while not deterministic - is not unbounded / won't go to that
times. I am of course using mlockall and everything. OTOH a priority
inversion case is a sure recipe for missing the deadlines.
Thank you for the pointer to the TLSF, this is very interesting project
and I will surely investigate this.
> You can probably get the replacement malloc be used by glibc by using
> LD_PRELOAD techniques (but OK, it would be just a hack).
Yes, this is possible but is indeed quite a hack.
Thanks
--
Stano
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
