From owner-freebsd-arch@FreeBSD.ORG Thu Dec 20 10:49:36 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E9787841 for ; Thu, 20 Dec 2012 10:49:36 +0000 (UTC) (envelope-from freebsd-arch@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 96ACD8FC0A for ; Thu, 20 Dec 2012 10:49:36 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TldhB-0004z4-Hu for freebsd-arch@freebsd.org; Thu, 20 Dec 2012 11:49:45 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 20 Dec 2012 11:49:45 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 20 Dec 2012 11:49:45 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-arch@freebsd.org From: Ivan Voras Subject: Re: Unmapped I/O Date: Thu, 20 Dec 2012 11:49:18 +0100 Lines: 37 Message-ID: References: <20121219135451.GU71906@kib.kiev.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig672A5CF2041B938E8336E022" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120812 Thunderbird/14.0 In-Reply-To: <20121219135451.GU71906@kib.kiev.ua> X-Enigmail-Version: 1.4.3 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2012 10:49:37 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig672A5CF2041B938E8336E022 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 19/12/2012 14:54, Konstantin Belousov wrote: > Besides not mapped buffers, not mapped BIOs are introduced, marked > with the flag BIO_NOTMAPPED. Unmapped buffers are directly translated > to unmapped BIOs. Geom providers may indicate an acceptance of the > unmapped BIOs. If provider does not handle unmapped i/o requests, > geom now automatically establishes transient mapping for the i/o > pages. Hi, Can you write up more details on what this means for GEOM developers: what is to be gained / lost (on GEOM level) for existing GEOM classes, and how to "indicate acceptance" for umapped BIOs? --------------enig672A5CF2041B938E8336E022 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDS7S8ACgkQ/QjVBj3/HSyhmQCfSxnxOEfWaZTnx+IIgZ4sv+Ev fxUAnRIHLBgaSCtkZQdYMyRjrKEG9iK+ =QbNP -----END PGP SIGNATURE----- --------------enig672A5CF2041B938E8336E022--