From owner-freebsd-arch@FreeBSD.ORG Sun May 10 05:13:04 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 1C49A1065670 for ; Sun, 10 May 2009 05:13:04 +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 C39268FC08 for ; Sun, 10 May 2009 05:13:03 +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 n4A50IwZ050729; Sun, 10 May 2009 01:00:18 -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 n4A50GOa050728; Sun, 10 May 2009 01:00:16 -0400 (EDT) (envelope-from wollman) Date: Sun, 10 May 2009 01:00:16 -0400 (EDT) From: Garrett Wollman Message-Id: <200905100500.n4A50GOa050728@hergotha.csail.mit.edu> To: scholz@scriptolutions.com X-Newsgroups: mit.lcs.mail.freebsd-arch In-Reply-To: References: Organization: None X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hergotha.csail.mit.edu [127.0.0.1]); Sun, 10 May 2009 01:00:18 -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: Re[2]: 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: Sun, 10 May 2009 05:13:04 -0000 In scholz@scriptolutions.com writes: >JT> shm_open/shm_unlink refer to the filesystem; they are fairly direct >JT> wrappers around open and unlink. > >Question is where are they stored? In the fileststem, in the path that you specify. They are just ordinary files. There was some thought that this was a bad (or at least not-like-Linux) way of implementing this feature, so I believe more-recent versions of FreeBSD do it differently. When I wrote this code, I could not see any reason for the "path" argument to be interpreted differently from any other path. -GAWollman