Messages in this thread | | | Subject | re: [PATCH] new timeout behavior for RPC requests on TCP sockets | From | Alan Cox <> | Date | 13 Nov 2002 17:42:28 +0000 |
| |
On Wed, 2002-11-13 at 16:44, Richard B. Johnson wrote: > If the application "chooses to drop the request", the kernel is not > required to fix that application. The RPC cannot retransmit if > it has been shut-down or disconnected, which is about the only > way the application could "choose to drop the request". So something > doesn't smell right here.
Check your socks...
As far as RPC goes the RPC server can choose to drop a request whenever it pleases by simply throwing it away (eg reading it from the socket and binning it) depending on its workload. There are actually reasons for that in some situations (eg if the top requests are all for a volume that is down its better to throw them away so you can get requests for a volume that is functional)
Alan
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |