Tzachi Dar wrote on Wed, 10 Mar 2010 at 00:04:10 > >> ND for some odd reason wants a successful return code for a >> failed disconnect call. If a Disconnect() call fails, allow >> it to be retried. Return STATUS_TIMEOUT - a 'successful' >> failure, rather than STATUS_IO_TIMEOUT, which is a 'failed' failure. >> (I love Windows, really, I do.) A subsequent call to EP: >> Disconnect() after a timeout will force the QP into the error >> state and force the EP into the disconnected state. > > In my experience all the ioctls should be returned as SUCCESS (or > pending). In the returned buffer have a variable that is the real > status. This will allow you to pass data from the kernel to the user > without having to deal with windows way of reporting errors ...
You can't do that, because the user receives the I/O completion. The user is first in line to see the error, and the drivers only get a chance to interpret the error after the user. -Fab _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
