Mad speculation: preallocating synthetic reply messages #67
Description
KBUS has various places where it is a very Bad Thing to fail a malloc. Some of
them are in the generation of synthetic messages, which are generally used to
send a "reply not going to happen" sort of message.
We really really want to be able to guarantee such messages will happen.
Two thoughts occur:
1. Since synthetic messages use a few predetermined message names, maybe we
shouldn't copy those names, but should instead just use a reference to the
static name. Of course, we'd have to note that and not free them.
2. Most synthetic messages don't have any data. Let's ignore the ones that do.
3. Maybe when a sender sends a request, as well as pre-allocating room on the
sender's message queue for the reply, we should also pre-allocate a synthetic
message, in case it is needed. Then we coudn't run out of malloc-space when we
do need one. See, I said it was mad. Seriously, this is a fair overhead to add
to any request sent, but it might be worth looking into.
Original issue reported on code.google.com by t...@tibsnjoan.co.uk on 7 Aug 2011 at 5:06