Problem with async-echo test

[Volker Lendecke]

On Wed, Jul 27, 2011 at 09:07:59PM +0200, Volker Lendecke wrote:
> > This is really the proposed clean way for this problem?
> 
> Just FYI: It does fix the problem, thanks a lot for the
> quick response!
> 
> It's just that I doubt this is the right place to fix it.
> To me it is really surprising that the requests are
> re-ordered on their way to the network, the necessity to run
> tevent_loop_once until a cifs request shows up on the
> cli_state is pretty surprising t me. We control everything
> from the API callers to the socket calls, what we do not
> control is the server side.  It is absolutely expected that
> the server is allowed to re-arrange its replies. Why this is
> allowed to happen within the libsmb and librpc code locally
> that we control 100% is not really transparent to me.

Question: I need to extend that test now and intermix rpc
sleep requests with outstanding write&x and echo requests.
Is there a way to make sure they are sent out to the wire in
the order the caller does them, or does the design of the s3
client library not allow this?

Thanks,

Volker

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen