Date: Sun, 8 Apr 2012 22:41:16 +0900 From: rozhuk.im@gmail.com To: "'Ivan Voras'" <ivoras@freebsd.org>, "'freebsd-hackers'" <freebsd-hackers@freebsd.org> Subject: RE: Socket buffer usage Message-ID: <4f819587.a894700a.4590.2270@mx.google.com> In-Reply-To: <CAF-QHFWV%2ByV3VwY3dhhxzi4=xwrJcUDULW=PyJxQH8Vb=61%2BSw@mail.gmail.com> References: <CAF-QHFWV%2ByV3VwY3dhhxzi4=xwrJcUDULW=PyJxQH8Vb=61%2BSw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
ioctl(FIONREAD) > -----Original Message----- > From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd- > hackers@freebsd.org] On Behalf Of Ivan Voras > Sent: Sunday, April 08, 2012 6:17 AM > To: freebsd-hackers > Subject: Socket buffer usage > > Hi, > > I'm tracking down an obscure bug in my userland program and it might > have something to do with the way I write&read data through a (Unix > domain) socket. I'm setting SO_SNDBUF and SO_RCVBUF, and what I'm > looking for is some way to query the amount of TX & RX buffered / free > data on a socket. Is there something I can use? I'll even accept > inspecting kernel structures if explained in detail and can be done on > a running system. > > Alternatively, is there anything else which could cause poll(2) with > POLLOUT on a socket to return no events ready on such a socket? (my > expectation being that a socket is always ready to be written to if > there is buffer space free...). > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers- > unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4f819587.a894700a.4590.2270>