From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753081AbXCRGdM (ORCPT ); Sun, 18 Mar 2007 02:33:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753084AbXCRGdL (ORCPT ); Sun, 18 Mar 2007 02:33:11 -0400 Received: from smtpout.mac.com ([17.250.248.177]:60816 "EHLO smtpout.mac.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753080AbXCRGdK (ORCPT ); Sun, 18 Mar 2007 02:33:10 -0400 In-Reply-To: <20070316171141.7a4de504@lxorguk.ukuu.org.uk> References: <20070316153408.3a9a244a@lxorguk.ukuu.org.uk> <20070316151305.04cbc352@lxorguk.ukuu.org.uk> <20070316125008.3740.44693.stgit@warthog.cambridge.redhat.com> <25571.1174054993@redhat.com> <26525.1174058071@redhat.com> <20070316171141.7a4de504@lxorguk.ukuu.org.uk> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <076F1B35-BE08-41B4-8294-581EDAFF4ACC@mac.com> Cc: David Howells , davem@davemloft.net, netdev@vger.kernel.org, herbert.xu@redhat.com, linux-kernel@vger.kernel.org, hch@infradead.org, arjan@infradead.org Content-Transfer-Encoding: 7bit From: Kyle Moffett Subject: Re: [PATCH 0/5] [RFC] AF_RXRPC socket family implementation [try #2] Date: Sat, 17 Mar 2007 23:32:17 -0700 To: Alan Cox X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mar 16, 2007, at 10:11:41, Alan Cox wrote: >> I know what they are; and I don't think that what's available >> covers it. >> >>> and use a proper standard socket type. >> >> Assuming that that list is exhaustive... > > SOCK_RDM seems to match perfectly well here. The point isn't to > enumerate everything in the universe the point is to find "works > like" parallels good enough to avoid more special casing. IMHO the problem with classifying RxRPC as a "reliable datagram" socket is that even an atomic unidirectional communication isn't a single datagram, it's at least 3; there is shared connection state and security context on both sides which pertains to a collection of independent and possibly simultaneous RxRPC calls. From the digging around that I did in the kernel socket code a while ago I don't see a cleaner way of implementing it than a new SOCK_RXRPC. Cheers, Kyle Moffett