From owner-freebsd-current@FreeBSD.ORG Tue May 16 08:24:09 2006 Return-Path: X-Original-To: current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50B3516A401 for ; Tue, 16 May 2006 08:24:09 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from sippysoft.com (gk.360sip.com [72.236.70.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9FA343D49 for ; Tue, 16 May 2006 08:24:08 +0000 (GMT) (envelope-from sobomax@sippysoft.com) Received: from sippysoft.com (localhost.360sip.com [127.0.0.1]) by sippysoft.com (8.13.6/8.13.6) with ESMTP id k4G8O7kj032995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 May 2006 01:24:07 -0700 (PDT) (envelope-from sobomax@sippysoft.com) Received: (from sobomax@localhost) by sippysoft.com (8.13.6/8.13.6/Submit) id k4G8O6ve032994; Tue, 16 May 2006 01:24:06 -0700 (PDT) (envelope-from sobomax) Date: Tue, 16 May 2006 01:24:06 -0700 From: Maxim Sobolev To: Poul-Henning Kamp Message-ID: <20060516082406.GA32353@gk.360sip.com> References: <4468DC05.9080808@sippysoft.com> <4488.1147758036@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4488.1147758036@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i Cc: "current@freebsd.org" Subject: Re: Optional mmap(2) support for geom(4) providers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2006 08:24:09 -0000 On Tue, May 16, 2006 at 07:40:36AM +0200, Poul-Henning Kamp wrote: > In message <4468DC05.9080808@sippysoft.com>, Maxim Sobolev writes: > >Poul-Henning Kamp wrote: > >> In message <44681D92.80309@sippysoft.com>, Maxim Sobolev writes: > >>> Hi, > >>> > >>> I would like to extend md(4) with support for mmap(4) operations, > >> > >> Uhm, how exactly would that work ? > > > >Just like ioctl(2) works: geom_dev will accept mmap requests and pass it > >to the underlying provider for execution if that provider has mmap > >handler in its g_class. > > No, I meant: how will you use this ? Well, in my particular case I would like to experiment with dynamic exporting of shared ELF objects from the kernel into userspace. md(4) seems like a good fit, but dlopen(3) uses mmap, so that it doesn't work OOB. There can be other uses as well. -Maxim