On 15 January 2013 11:34, Alexander Bluhm <alexander.bl...@gmx.net> wrote: > Hi, > > Some years ago reyk@ mentioned that the current socket splicing > semantics is suboptimal. When used with persistent http connections, > the kernel does not inform user land when the maximum splicing > lenght has been reached. The file descriptor does not get active > when the last byte within the limit has been spliced, but only after > additional data has arrived. > > When mikeb@ implemented idle timeouts, he had the idea to pass an > ETIMEDOUT error to user land. This creates an event on the socket > that can be checked with select(2). Similary this diff passes an > EFBIG error when the maximum splicing length is reached. So the > kernel passes control to user land immediately. This can be used > to log the end of an http request. > > reyk@, mikeb@: What do you think about this idea? > > bluhm >
i support your idea and think you should go ahead with it.
