From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hannes Frederic Sowa Subject: Re: Add a SOCK_DESTROY operation to close sockets from userspace Date: Thu, 19 Nov 2015 16:54:29 +0100 Message-ID: <1447948469.2030778.444426889.4F4A5648@webmail.messagingengine.com> References: <20151118.153508.123902005995190872.davem@davemloft.net> <1447879416.562854.443622857.62708268@webmail.messagingengine.com> <20151118.224919.452852815199526735.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Lorenzo Colitti , Eric Dumazet , Stephen Hemminger , Linux Kernel Network Developers , Eric Dumazet , Erik Kline , =?UTF-8?Q?Maciej=20=C5=BBenczykowski?= , Dmitry Torokhov To: Tom Herbert , David Miller Return-path: Received: from out5-smtp.messagingengine.com ([66.111.4.29]:50154 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934018AbbKSPyd (ORCPT ); Thu, 19 Nov 2015 10:54:33 -0500 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 34A782075E for ; Thu, 19 Nov 2015 10:54:30 -0500 (EST) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Nov 19, 2015, at 06:12, Tom Herbert wrote: > I think this solution presumes some out of band signaling about a path > failure deep in the network that is not reported via the TCP > connection. This solution is obviously only as good as the signaling, > but clearly the most general solution to maintaining reachability has > been (and unfortunately will probably continue to be) application > keepalives. Ack. With emphasis of *application*. :)