From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753264Ab0C2PEW (ORCPT ); Mon, 29 Mar 2010 11:04:22 -0400 Received: from nlpi129.sbcis.sbc.com ([207.115.36.143]:52926 "EHLO nlpi129.prodigy.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751441Ab0C2PEV (ORCPT ); Mon, 29 Mar 2010 11:04:21 -0400 Date: Mon, 29 Mar 2010 10:00:57 -0500 (CDT) From: Christoph Lameter X-X-Sender: cl@router.home To: Andi Kleen cc: David Miller , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Add PGM protocol support to the IP stack In-Reply-To: <20100327131138.GD20695@one.firstfloor.org> Message-ID: References: <87tysccjrn.fsf@basil.nowhere.org> <20100322163609.GZ20695@one.firstfloor.org> <877hp4i76d.fsf@basil.nowhere.org> <20100322185310.GA20695@one.firstfloor.org> <20100327131138.GD20695@one.firstfloor.org> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 27 Mar 2010, Andi Kleen wrote: > On Fri, Mar 26, 2010 at 12:33:07PM -0500, Christoph Lameter wrote: > > Here is a pgm.7 manpage describing how the socket API could look like for > > a PGM implementation. > > > > I dumped the RM_* based socket options from the other OS since most of the > > options were unusable. > > I did a quick read and the manpage/interface seem reasonable to me. Thanks. I will then proceed to get a patch out that implements the network environment. Then we can plug the openpgm logic in there. > You changed the parameter struct fields to lower case. While > that looks definitely more Linuxy than before does it mean programs > have to #ifdef this? It might be good idea to have at least some > optional compat header that #defines. The socket API will be completely different. The basic handling of the sockets is the same (binding, listening, connecting). There is no way of mapping M$ socket options to Linux socket options with the approach that I proposed in the manpage. The stats structure is different too since some key elements were missing. What users are there of the M$ api? I have seen vendors supplying their own pgm implementation (guess due to bit rot in the old M$ implementation).