From owner-freebsd-arch@FreeBSD.ORG Mon May 11 16:35:44 2009 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 634B61065670 for ; Mon, 11 May 2009 16:35:44 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (hergotha.csail.mit.edu [66.92.79.170]) by mx1.freebsd.org (Postfix) with ESMTP id 0F3788FC1C for ; Mon, 11 May 2009 16:35:43 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.2/8.14.2) with ESMTP id n4BGZeIZ066201; Mon, 11 May 2009 12:35:40 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.2/8.13.8/Submit) id n4BGZerd066198; Mon, 11 May 2009 12:35:40 -0400 (EDT) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18952.21468.748665.878710@hergotha.csail.mit.edu> Date: Mon, 11 May 2009 12:35:40 -0400 From: Garrett Wollman To: Lothar Scholz In-Reply-To: <1393224851.20090511112537@scriptolutions.com> References: <200905100500.n4A50GOa050728@hergotha.csail.mit.edu> <7710650619.20090510075706@scriptolutions.com> <18950.63671.323324.756287@hergotha.csail.mit.edu> <1393224851.20090511112537@scriptolutions.com> X-Mailer: VM 7.17 under 21.4 (patch 21) "Educational Television" XEmacs Lucid X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hergotha.csail.mit.edu [127.0.0.1]); Mon, 11 May 2009 12:35:41 -0400 (EDT) X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on hergotha.csail.mit.edu Cc: arch@freebsd.org Subject: Re: Posix shared memory problem X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2009 16:35:46 -0000 < said: > Some idiots started to think about this as a file path. But it isn't > and it shouldn't. Actually, it really should be. Ask a security person or a virtualization person to explain why an unnecessary multiplicity of namespaces is a bad idea. > If i have to find a useable filefile location anyway the whole > function does not make any sense, then i can directly use mmap. But of course you won't get the same behavior, because open()/mmap() guarantees that the backing store will get updated. That's why there's a separate interface. -GAWollman