Date: Fri, 10 Jan 2003 10:51:21 -0800 From: "Sam Leffler" <sam@errno.com> To: "Nate Lawson" <nate@root.org> Cc: <current@FreeBSD.ORG>, <re@FreeBSD.ORG> Subject: Re: Serious issues with kqueue on sockets on CURRENT. Message-ID: <009701c2b8d9$44a010f0$5a557f42@errno.com> References: <Pine.BSF.4.21.0301101036310.24355-100000@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Fri, 10 Jan 2003, Sam Leffler wrote:
> > unless the mbufs are specifically tagged as such. I'm not clear on
exactly
> > what sb_ctl is supposed to count; the comment in the cvs log is unclear:
> >
> > "Track the number of non-data chararacters stored in socket buffers so
that
> > the data value returned by kevent()'s EVFILT_READ filter on non-TCP
> > sockets accurately reflects the amount of data that can be read from the
> > sockets by applications."
> >
> > What are "non-data characters"?
>
> A very zen question. :) In this case, It probably means bytes carried in
> an mbuf with a type other than MT_DATA.
The point was that it's not clear to me that you can infer this data from
the inverse set of (MT_DATA +whatever). Garrett suggested MT_SONAME data as
an example of non-data characters. I no longer know exactly what the
complete set of mbuf types is that comprise "non-data characters".
Sam
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?009701c2b8d9$44a010f0$5a557f42>