From: Gerrit Renker Subject: Re: [PATCH 2.6.17-rc6-mm1 ] net: RFC 3828-compliant UDP-Lite support Date: Thu, 8 Jun 2006 17:03:54 +0100 Message-ID: <200606081703.55361.gerrit@erg.abdn.ac.uk> References: <200606081150.34018@this-message-has-been-logged> <1149778072.22124.6.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Cc: davem@davemloft.net, kuznet@ms2.inr.ac.ru, pekkas@netcore.fi, jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@coreworks.de, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Return-path: Received: from dee.erg.abdn.ac.uk ([139.133.204.82]:19362 "EHLO erg.abdn.ac.uk") by vger.kernel.org with ESMTP id S964892AbWFHQEi (ORCPT ); Thu, 8 Jun 2006 12:04:38 -0400 To: Alan Cox In-Reply-To: <1149778072.22124.6.camel@localhost.localdomain> Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Quoting Alan Cox: | Ar Iau, 2006-06-08 am 11:50 +0100, ysgrifennodd Gerrit Renker: | > + UDP-Lite introduces a new socket type, the SOCK_LDGRAM (note the L) for | > + lightweight, connection-less services. These are the socket options: | | This is not the intended use of the socket API when distinguishing | between services. The socket() call has a protocol field that is usually | unused and it exists precisely to disambiguate multiple protocols with | the same generic behaviour but different properties. | | s = socket(PF_INET, SOCK_DGRAM, IPPROTO_UDPLITE); | | is probably the right way to do this, keeping 0 "default" as before | meaning IPPROTO_UDP Understood. Please, anyone, disregard or un-apply the previous UDP-Lite patch. A revised patch will be prepared and posted as soon as testing permits.