Re: [omega-g1:11072] Re: [PATCH] net: configurable sysctl parameter"net.core.tcp_lowat" for sk_stream_min_wspace()

[Jun.Kondo]

By using this patch, we want to prevent "timeout occured over the network that is low throughput but available".

But in the current implementation, both blocking and non-blocking,
user processes can't recognize the reason in detail
when failed to write to socket buffer, we think.

is it (really) network problem ?
or is wmem not enough free to write?

As stated above, we think it is difficult for user processes to handle timeout of writing socket buffer,
when wmem is configured large value.(to ensure high throughput over the high ralency network, like 3G).


(2011/08/19 18:43), David Miller wrote:
> From: "Jun.Kondo"<jun.kondo@xxxxxxxxxxx>
> Date: Fri, 19 Aug 2011 18:28:45 +0900
>
> > You suggested to use non-blocking writes, but we think
> > we have to rewrite the Apache code if doing so.
> > That is, we have to make a modification to Apache that
> > depends on the architecture.
> > By using this patch, it can be handled by changing the
> > configuration a little bit on the kernel side for such
> > applications that it is difficult to do so on application
> > side.
> The kernel provides the facilities necessary to achieve your
> goals.  It is a userspace problem.


--
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
èèãæ
v äèåãããããããããããæåäç(CTC)
v ããããæèç1éãæèç4è
v åä:03-6757-2144
v FAX:03-5800-2256
v
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/