Date: Thu, 15 Jun 2000 14:50:27 -0500 From: Jason Young <jyoung@accessus.net> To: 'Alfred Perlstein' <alfred@FreeBSD.ORG>, Nate Williams <nate@yogotech.com> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: RE: cvs commit: src/sys/kern uipc_socket.c uipc_socket2.c src/sys /sys socket.h Message-ID: <AFD8E724533ED4119EEB00508B9A2140CEE7@exchange.accessus.net>
next in thread | raw e-mail | index | archive | help
> > Also, I *really* don't like the accept() changes, since we > (and a number > > of others) are currently taking advantage of the fact that > we can 'ping' > > a host by contacting a known port and if accepts the > connection, which > > we subsuquently close. > > > > ICMP is often filtered, but in our equipment (which happens to be > > installed the customer's site), we run a the 'echo' port for our > > internal ping. > > > > Waiting until data is sent (or received) is a bad thing, IMO, and > > probably violates the TCP specifications. > > That's not what the code does, nothing funky happens with TCP > connections, the socket is accepted, however it is not presented > to the application until data arrives. I think perhaps Nate is under the impression that it's a global change for all connections, whereas it's really a new and non-default socket option if I understand correctly. The impact is that an application which does not need to present a "banner" (SMTP requires one, for instance) can defer being woken up until it actually has work to do, and other applications are untouched. I think both kblob and the new socket options are great ideas myself, but I have about zero votes in this whole affair. I would think that a mechanism to give the kernel a pattern to look for instead of only looking for HTTP requests would be nice, but I'm not sure if a useful mechanism could be developed without trying to install regexp processing in the kernel. Jason Young Access US Chief Network Engineer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AFD8E724533ED4119EEB00508B9A2140CEE7>