From owner-freebsd-current@FreeBSD.ORG Mon May 15 17:01:10 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 2D2B216A9D2 for ; Mon, 15 May 2006 17:01:10 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk.360sip.com [72.236.70.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1B0643D67 for ; Mon, 15 May 2006 17:01:06 +0000 (GMT) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.0.38] ([204.244.149.125]) (authenticated bits=0) by sippysoft.com (8.13.6/8.13.6) with ESMTP id k4FH0wXU021050 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 May 2006 10:00:59 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Message-ID: <4468B3C8.8010707@FreeBSD.org> Date: Mon, 15 May 2006 10:00:56 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Ivan Voras References: <44681D92.80309@sippysoft.com> <4468AA73.9000702@fer.hr> In-Reply-To: <4468AA73.9000702@fer.hr> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit 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: Mon, 15 May 2006 17:01:10 -0000 Ivan Voras wrote: > Maxim Sobolev wrote: >> Hi, >> >> I would like to extend md(4) with support for mmap(4) operations, >> however it's interfaced to the world via geom_dev(4), which doesn't >> provide mmap pass-through interface. Is it intentional or not? Are you >> willing to accept the patches if I do the actual work? > > Just an opinion: It would probably be more useful to implement mmap at a > lower level (GEOM) so all devices can use it. I am not sure that I understand what do you mean. In the case of md(4) mmap makes huge sense, since for preloaded images your disk in fact is just range of kernel memory, so that doing mmap is trivial. -Maxim