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
Date: Fri, 6 Sep 2002 12:21:24 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: Contemplating drastic change to mount handling
Message-ID: <20020906162124.GK21699@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20020906030958 DOT GA27496 AT redhat DOT com> <1031329123 DOT 1363 DOT 46 DOT camel AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1031329123.1363.46.camel@lifelesswks>
User-Agent: Mutt/1.4i

On Sat, Sep 07, 2002 at 02:18:43AM +1000, Robert Collins wrote:
>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). 

I thought about that but mmaping a file works much nicer.

>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.

The big problem with normal tries is their space consumption.  I
have something hacked together which works around that to some
degree.

cgf