Date: Sun, 8 Apr 2012 23:33:24 -0400 From: Yoshihiro Ota <ota@j.email.ne.jp> To: freebsd-hackers@freebsd.org Subject: Re: Socket buffer usage Message-ID: <20120408233324.77d24491.ota@j.email.ne.jp> In-Reply-To: <CAF-QHFWqkNkzmEN-GBnMO4porVub1CQZRLkudMVbP7d1hdEhxQ@mail.gmail.com> References: <CAF-QHFWV%2ByV3VwY3dhhxzi4=xwrJcUDULW=PyJxQH8Vb=61%2BSw@mail.gmail.com> <0D2E65B3D0AB4A6483C26A613FC73F83@dudu.ro> <CAF-QHFWqkNkzmEN-GBnMO4porVub1CQZRLkudMVbP7d1hdEhxQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 8 Apr 2012 01:01:01 +0200 Ivan Voras <ivoras@freebsd.org> wrote: > On 7 April 2012 23:36, Vlad Galu <dudu@dudu.ro> wrote: > > This might not exactly be what you want, but struct kevent has a member called "data" which, > > for sockets and pipes, returns the number of available bytes to read (or write) for EVFILT_READ > > (or EVFILT_WRITE) events. > > > > That's a good idea but I'm actually trying to find out why my write > events are not firing, so I can't get to that information. Do you happen to use 2 TCP connections in threaded client/server programs: one for reading only and the other for writing only? If so, I observed such behavior in several years ago and can give you a hint. Hiro
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120408233324.77d24491.ota>