From owner-p4-projects@FreeBSD.ORG  Tue Oct 23 22:31:39 2007
Return-Path: <owner-p4-projects@FreeBSD.ORG>
Delivered-To: p4-projects@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id D1DAA16A46D; Tue, 23 Oct 2007 22:31:38 +0000 (UTC)
Delivered-To: perforce@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 830F616A420
	for <perforce@freebsd.org>; Tue, 23 Oct 2007 22:31:38 +0000 (UTC)
	(envelope-from julian@elischer.org)
Received: from outF.internet-mail-service.net (outF.internet-mail-service.net
	[216.240.47.229])
	by mx1.freebsd.org (Postfix) with ESMTP id 77E7F13C481
	for <perforce@freebsd.org>; Tue, 23 Oct 2007 22:31:38 +0000 (UTC)
	(envelope-from julian@elischer.org)
Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160)
	by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP;
	Tue, 23 Oct 2007 15:31:08 -0700
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100])
	by idiom.com (Postfix) with ESMTP id BCAA71267BD;
	Tue, 23 Oct 2007 15:31:07 -0700 (PDT)
Message-ID: <471E7645.1030503@elischer.org>
Date: Tue, 23 Oct 2007 15:31:33 -0700
From: Julian Elischer <julian@elischer.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Marko Zec <zec@icir.org>
References: <200710230018.l9N0IO8l020652@repoman.freebsd.org>
	<471D4514.5050109@elischer.org> <200710232314.38149.zec@icir.org>
In-Reply-To: <200710232314.38149.zec@icir.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Perforce Change Reviews <perforce@freebsd.org>, Marko Zec <zec@freebsd.org>
Subject: Re: PERFORCE change 127942 for review
X-BeenThere: p4-projects@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: p4 projects tree changes <p4-projects.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/p4-projects>
List-Post: <mailto:p4-projects@freebsd.org>
List-Help: <mailto:p4-projects-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2007 22:31:39 -0000

Marko Zec wrote:
> On Tuesday 23 October 2007 02:49:24 Julian Elischer wrote:
>> question:
>>
>> can processes in two vimages communicate if they both have access
>> to the same named pipe/fifo in the filesystem?
> 
> Yes, provided that they open the fifo while they would be both attached 
> to the same vnet.  Once the sockets would become open the processes 
> could reassociate to arbitrary vimages, while the sockets would remain 
> bound to their original vnets for their entire lifetime duration.
hmm that's not what I want... what I want is an ability for processes in two overlapping
vimages to communicate easily without incuring the overhead of going throigh a virtual router.
another possibility is a local: interface (address 127.1.[vnet number]) which acts like
a local net  between the virtual machines.

> 
> As an alternative, we could / should introduce an extended socket() 
> syscall where an additional argument would explicitly specify to which 
> vimage/vnet the new socket should belong.

if a process in the root vimage makes fifo in /vimages/vimage1/usr/tmp/fifo1

and a process in vimage1 (that is chrooted at /vimages/vimage1/)
opens the fifo at /usr/tmp/fifo1

why can't they communicate?  I'm surprised at this..

> 
> Marko