Messages in this thread | | | Subject | Re: SO_SNDBUF makes select() hang | From | <> | Date | Sat, 27 Jul 1996 11:50:51 -0400 (EDT) |
| |
> > Hm, while playing with setting SO_SNDBUF through setsockopt() I noticed > > this behavior: if SO_SNDBUF is set low (I was trying 128) then select() > > won't ever show the socket as available for writing. > > We handle our send/receive buffers as including header sizes (ie sk_buff > struct overhead) and the like. That means setting ultra low values won't > work nicely for all sorts of pathalogical cases.
For cases like this, why not have setsockopt() return -EINVAL. Breaking the code there is better than a infite block.
| |