Optimise the Luxi.recvMsg function
Optimise the Luxi.recvMsg function

Since the current buffer cannot contain (during network reads) an EOM,
we should look for the EOM only in the newly-received string.  While
this shouldn't make much difference, in some tests it cuts the recvMsg
total time by around half.

On entering recvMsg, we have though to search the old buffer for a
message though, since we could have received two Luxi messages on the
last network query; this is however a one-off cost, compared to
continuously looking for the EOM in the old string (at each receive
loop).

yiannist/ganeti,dimara/ganeti,grnet/snf-ganeti,yiannist/ganeti,ganeti/ganeti,dimara/ganeti,apyrgio/snf-ganeti,bitemyapp/ganeti,onponomarev/ganeti,grnet/snf-ganeti,apyrgio/ganeti,leshchevds/ganeti,ganeti/ganeti,mbakke/ganeti,apyrgio/snf-ganeti,apyrgio/ganeti,mbakke/ganeti,yiannist/ganeti,andir/ganeti,ganeti-github-testing/ganeti-test-1,ganeti-github-testing/ganeti-test-1,mbakke/ganeti,bitemyapp/ganeti,leshchevds/ganeti,onponomarev/ganeti,leshchevds/ganeti,andir/ganeti,andir/ganeti,ganeti/ganeti