> As for needing a longer timeout - in our old proprietary stack, QLogic did > have a longer timeout for retrying busy replies than for normal timeouts - > but we should try to get this in now so we can get some relief before we > begin the long term discussion of the best way to handle this issue > overall.
Because applications may handle BUSY replies differently, we shouldn't simply start hiding them from the user. I would much rather agree on the longer term plan, so that the ABI can reflect the proper semantics. I don't see any issue with changing the current behavior for kernel clients, however. - Sean
