Date: Tue, 14 Sep 2010 18:22:45 +0200 From: Andre Oppermann <oppermann@networx.ch> To: Fabien Thomas <fabien.thomas@netasq.com> Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: TCP loopback socket fusing Message-ID: <4C8FA155.8050602@networx.ch> In-Reply-To: <89E74A8F-4FF9-482B-83D0-3D076F0E41E4@netasq.com> References: <4C8E0C1E.2020707@networx.ch> <A9862681-6A4D-43A3-9A26-C71A54CF86F0@netasq.com> <4C8F978F.1030707@networx.ch> <89E74A8F-4FF9-482B-83D0-3D076F0E41E4@netasq.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14.09.2010 18:08, Fabien Thomas wrote: > > On 14 sept. 2010, at 17:41, Andre Oppermann wrote: > >> On 14.09.2010 11:18, Fabien Thomas wrote: >>> Great, >>> >>> This will maybe kill the long time debate about "my loopback is slow vs linux" >>> To have the best of both world what about a socket option to enable/disable fusing: >>> can be useful when you need to see some connection "packetized". >> >> A sysctl to that effect is already in the patch. > yes, i'm just wondering on a per connection setting. I've devised a way to prevent socket fusing when bpf is enabled on the interface the loopback came from. So I'm leaning against adding another obscure and non-portable socket option. -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C8FA155.8050602>