From owner-freebsd-geom@FreeBSD.ORG Sat Mar 21 00:08:20 2009 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 970A71065678 for ; Sat, 21 Mar 2009 00:08:20 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 1B8CF8FC17 for ; Sat, 21 Mar 2009 00:08:19 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LkoF7-0005cH-Fx for freebsd-geom@freebsd.org; Fri, 20 Mar 2009 23:35:13 +0000 Received: from 93-141-34-15.adsl.net.t-com.hr ([93.141.34.15]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Mar 2009 23:35:13 +0000 Received: from ivoras by 93-141-34-15.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Mar 2009 23:35:13 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-geom@freebsd.org From: Ivan Voras Date: Sat, 21 Mar 2009 00:34:37 +0100 Lines: 58 Message-ID: References: <20090319081936.GA32750@onelab2.iet.unipi.it> <20090319130137.GB40489__3492.42561865157$1237467521$gmane$org@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigBF64D510A73AEB49CE90CB48" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 93-141-34-15.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: <20090319130137.GB40489__3492.42561865157$1237467521$gmane$org@onelab2.iet.unipi.it> X-Enigmail-Version: 0.95.7 Sender: news Subject: Re: RFC: adding 'proxy' nodes to provider ports (with patch) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Mar 2009 00:08:22 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBF64D510A73AEB49CE90CB48 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Luigi Rizzo wrote: > On Thu, Mar 19, 2009 at 12:41:13PM +0100, Marius N?nnerich wrote: >> 2009/3/19 Luigi Rizzo : >>> Hi, >>> >>> Fabio Checconi and I have been thinking on how to implement "proxy" >>> geom nodes, i.e. nodes that have exactly 1 provider and 1 consumer >>> port, do not do any data transformation, and can be transparently >>> inserted or removed on top of a provider port while the tree is >>> actively moving data. > ... >>> The idea is to intercept requests coming on a provider port, pp, and >>> redirect them to a geom node acting as a proxy if the port >>> is configured in this way: > ... >> I wonder if it's really necessary to alter the GEOM infrastructure or >> if it is possible to do this with what's there already. Just an idea: >> Lock g_topology, put g_down and g_up to sleep, alter the consumer and >> provider pointers where you need it so the everything is routed >> through your proxy class (which isn't special in any way) and restart >> g_down and g_up. >=20 > we'll look into this, thanks. If we can spare the extra fields > in the g_provider, the thing is even easier to do. >=20 > I just don't know how your suggestion interferes with the naming: > if I change the pointers, the name of a provider will not > be anymore a prefix of the name of the node attached above. > But maybe that is not an architectural requirements but just > a convenient convention. Not only with naming and device creation - the proxy classes cannot be "normal" classes because it's common that "normal" classes do a lot of initialization in .taste. (i.e. there at least needs to be a flag for proxy classes) --------------enigBF64D510A73AEB49CE90CB48 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknEKBUACgkQldnAQVacBchKhwCg71ft9Jn6NaT9MErBc0PI0IN2 hakAoJrO2DBaW2YjDk0nbM3B2YMsP+Zw =cpco -----END PGP SIGNATURE----- --------------enigBF64D510A73AEB49CE90CB48--