Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Subject: Re: Contemplating drastic change to mount handling
From: Robert Collins <rbcollins AT cygwin DOT com>
To: cygwin-developers AT cygwin DOT com
In-Reply-To: <20020906030958.GA27496@redhat.com>
References: <20020906030958 DOT GA27496 AT redhat DOT com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-vojwz0T2t9QATcSFeFfY"
Date: 07 Sep 2002 02:18:43 +1000
Message-Id: <1031329123.1363.46.camel@lifelesswks>
Mime-Version: 1.0


--=-vojwz0T2t9QATcSFeFfY
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2002-09-06 at 13:09, Christopher Faylor wrote:
> This thinking came about due to some late night dabbling with tries as a
> method for scanning the mount table.  They hold great promise for this
> since they are fast and handle maximal matching with ease.  But, then I
> was wondering how I could easily store the trie in shared memory since
> it relies on pointers and sizing a trie ahead of time essentially
> requires building the trie first and then copying it into shared memory
> since we don't currently have a convenient method for allocating shared
> memory.

Why not store the trie in a binary blob in the registry? (I'm just
thinking of minimal change needed to get the benefit).=20

I really like the use of tries, I've been meaning to get time to
implement that for cygwin for ages. I dont' care either way about
/etc/fstab and /etc/mtab.

Rob

--=-vojwz0T2t9QATcSFeFfY
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA9eNViI5+kQ8LJcoIRAi5FAJ475Auta5NKUVVgKNeNh1auecozTgCfdd1e
8pmP4MXdlaYnFWqEayVQqnM=
=Ji3D
-----END PGP SIGNATURE-----

--=-vojwz0T2t9QATcSFeFfY--