public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Newall <david@davidnewall.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Renzo Davoli <renzo@cs.unibo.it>,
	Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org
Subject: Re: New Address Family: Inter Process Networking (IPN)
Date: Thu, 06 Dec 2007 17:29:55 +1030	[thread overview]
Message-ID: <47579DEB.9020102@davidnewall.com> (raw)
In-Reply-To: <2BD0AF2A-959D-4744-9D2A-3AE84CF96CBB@mac.com>

Kyle Moffett wrote:
> On Dec 06, 2007, at 00:30:16, Renzo Davoli wrote:
>> AF_IPN is different.  AF_IPN is the broadcast and peer-to-peer 
>> extension of AF_UNIX. It supports communication among *user* processes.
>
> Ok, you say it's different, but then you describe how IP unicast and 
> broadcast work.

Renzo also described something new (in the socket() arena): the 
multi-reader, multi-writer is just not available in IP.

I wonder if this solves the same problem as d-bus?


> So if you really think this is something that belongs in the kernel 
> you need to provide much more detailed descriptions and use-cases for 
> why it cannot be implemented in user-space or with small modifications 
> to existing UDP/TCP networking. 

I would strengthen this sentiment: If you think something belongs in the 
kernel, you need to argue your case (provide much more detailed 
descriptions and use-cases.)

  reply	other threads:[~2007-12-06  7:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05 16:40 New Address Family: Inter Process Networking (IPN) Renzo Davoli
2007-12-05 21:55 ` Stephen Hemminger
2007-12-06  5:38   ` Renzo Davoli
2007-12-06  5:43     ` Renzo Davoli
2007-12-06  6:04     ` Stephen Hemminger
2007-12-05 23:39 ` Andi Kleen
2007-12-06  5:30   ` Renzo Davoli
2007-12-06  6:19     ` Kyle Moffett
2007-12-06  6:59       ` David Newall [this message]
2007-12-06 16:34         ` Andi Kleen
2007-12-06 22:21           ` David Newall
2007-12-06 22:42             ` Andi Kleen
2007-12-06 16:35     ` Andi Kleen
2007-12-06 20:36       ` Chris Friesen
2007-12-06 21:26         ` Andi Kleen
2007-12-06 21:49           ` Chris Friesen
2007-12-06 22:07             ` Andi Kleen
2007-12-06 22:18               ` Renzo Davoli
2007-12-06 22:38                 ` Andi Kleen
2007-12-07  0:18                   ` Renzo Davoli
2007-12-06 23:02               ` Chris Friesen
2007-12-06 23:06                 ` Andi Kleen
2007-12-06 23:42                   ` Chris Friesen
2007-12-07  3:41         ` David Miller
2007-12-07  4:21           ` Chris Friesen
2007-12-07  4:54             ` Ben Pfaff
2007-12-07  6:40             ` David Miller
2007-12-07 10:03               ` Andi Kleen
2007-12-07 21:18                 ` AF_IPN: Inter Process Networking, try these Renzo Davoli
2007-12-08  2:07                   ` David Miller
2007-12-10 16:05               ` New Address Family: Inter Process Networking (IPN) Chris Friesen

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=47579DEB.9020102@davidnewall.com \
    --to=david@davidnewall.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --cc=renzo@cs.unibo.it \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox