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: Mon, 22 Mar 2010 17:36:09 +0100 [thread overview]
Message-ID: <20100322163609.GZ20695@one.firstfloor.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1003220916170.15360@router.home>
On Mon, Mar 22, 2010 at 09:20:42AM -0500, Christoph Lameter wrote:
> On Fri, 19 Mar 2010, Andi Kleen wrote:
>
> > Christoph Lameter <cl@linux-foundation•org> writes:
> > >
> > > I know about the openpgm implementation. Openpbm does this at the user
> > > level and requires linking to a library. It is essentially a communication
> > > protocol done in user space. It has privilege issues because it has to
> > > create PGM packets via a raw socket.
> >
> > That seems like a poor reason alone to put something into the kernel
> > Perhaps you rather need some way to have unpriviledged raw sockets?
>
> Not the only reason. There are also performance implications. NAKing and
> other control messages from user space are a pain and the available
> implementations add numerous threads just to control the timing of control
> messages and the expiration of data etc. Its difficult to listen to a PGM
> port from user space. You have to get all messages for the PGM protocol
> and then filter in each process.
Ok that sounds like a good reason to have a kernel protocol.
Thanks.
Multicast reliable kernel protocols are somewhat new, I guess one
would need to make sure to come up with a clean generic interface
for them first.
-Andi
--
ak@linux•intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-03-22 16:36 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 [this message]
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
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=20100322163609.GZ20695@one.firstfloor.org \
--to=andi@firstfloor$(echo .)org \
--cc=cl@linux-foundation$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox