[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110822.113544.28950168095176936.davem@davemloft.net>
Date: Mon, 22 Aug 2011 11:35:44 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jun.kondo@...-g.co.jp
Cc: linux-kernel@...r.kernel.org, omega-g1@...-g.co.jp,
notsuki@...hat.com, motokazu.kozaki@...com, htaira@...hat.com,
netdev@...r.kernel.org, tomohiko.takahashi@...-g.co.jp,
kotaro.sakai@...-g.co.jp, ken.sugawara@...-g.co.jp
Subject: Re: [omega-g1:11072] Re: [PATCH] net: configurable sysctl
parameter "net.core.tcp_lowat" for sk_stream_min_wspace()
From: "Jun.Kondo" <jun.kondo@...-g.co.jp>
Date: Mon, 22 Aug 2011 09:33:52 +0900
> is it (really) network problem ?
> or is wmem not enough free to write?
Oh yes you can indeed make this determination, by using the socket
timeouts via the SO_RCVTIMEO and SO_SNDTIMEO socket options.
Timeouts, when hit, will return -EINTR, whereas lack of buffer space
on a non-blocking socket will return -EAGAIN.
I think you simply are unaware of the facilities available in the BSD
socket API.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists