From: Andi Kleen <andi@firstfloor.org>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Add PGM protocol support to the IP stack
Date: Sat, 27 Mar 2010 14:11:39 +0100 [thread overview]
Message-ID: <20100327131138.GD20695@one.firstfloor.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1003261231410.30253@router.home>
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.
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.
-Andi
next prev parent reply other threads:[~2010-03-27 13:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 17:58 Add PGM protocol support to the IP stack Christoph Lameter
2010-03-18 21:58 ` Christoph Lameter
2010-03-19 17:18 ` Andi Kleen
2010-03-19 21:53 ` David Miller
2010-03-19 22:26 ` H. Peter Anvin
2010-03-22 14:24 ` Christoph Lameter
2010-03-22 14:20 ` Christoph Lameter
2010-03-22 16:36 ` Andi Kleen
2010-03-22 16:51 ` Christoph Lameter
2010-03-22 17:43 ` Andi Kleen
2010-03-22 18:07 ` Christoph Lameter
2010-03-22 18:53 ` Andi Kleen
2010-03-22 19:32 ` Christoph Lameter
2010-03-26 17:33 ` Christoph Lameter
2010-03-27 13:11 ` Andi Kleen [this message]
2010-03-27 16:54 ` Martin Sustrik
2010-03-29 14:50 ` Christoph Lameter
2010-03-29 15:00 ` Christoph Lameter
2010-03-29 21:43 ` Andi Kleen
2010-03-29 23:01 ` H. Peter Anvin
2010-03-30 18:12 ` Christoph Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100327131138.GD20695@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.