From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932453Ab2GAONE (ORCPT ); Sun, 1 Jul 2012 10:13:04 -0400 Received: from lxorguk.ukuu.org.uk ([81.2.110.251]:45894 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932418Ab2GAONC (ORCPT ); Sun, 1 Jul 2012 10:13:02 -0400 Date: Sun, 1 Jul 2012 15:16:59 +0100 From: Alan Cox To: David Miller Cc: vincent.sanders@collabora.co.uk, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: AF_BUS socket address family Message-ID: <20120701151659.2be61475@pyramind.ukuu.org.uk> In-Reply-To: <20120630.173346.670086962166528527.davem@davemloft.net> References: <20120629234230.GA11480@kyllikki.org> <20120629.165023.1605284574408858612.davem@davemloft.net> <20120630141222.60df95a5@pyramind.ukuu.org.uk> <20120630.173346.670086962166528527.davem@davemloft.net> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.8; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > The issue is that what to do when a receiver goes deaf is a policy > issue. Something all these protocols alredy recognize and have done for years. The real issue for AF_BUS versus the current slow AF_UNIX approach is that you really need to know *who* is blocked up. That's no different to UDP multicast and needing to know how errored the frame. Alan