Subject: Re: Variant symlink filesystem
To: Cole <cole@opteqint.net>
References: <CACsf_wyTqDyfwVnJeWC3ExO5Jeh5mjKxQP2HmJF6o9wuSXATaA@mail.gmail.com>
 <CAFLxGvwieXCTCOioFf9G8unzy4+e=QM8=eucWrqJpu2e5ULGBA@mail.gmail.com>
 <CACsf_ww2h6enKxSz5fCvwmipsyfBnwZeY78Vze8KHh8f-gUYjQ@mail.gmail.com>
 <56E327FF.1010103@nod.at>
 <CACsf_wwWZvu7YFomfB6S=iA24yFxjW9YcsDCmQTuPHod8+emCw@mail.gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
From: Richard Weinberger <richard@nod.at>
Message-ID: <56E3298A.1040008@nod.at>
Date: Fri, 11 Mar 2016 21:24:42 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CACsf_wwWZvu7YFomfB6S=iA24yFxjW9YcsDCmQTuPHod8+emCw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 463
Lines: 13

Am 11.03.2016 um 21:22 schrieb Cole:
> If I remember correctly, when we were testing the fuse version, we hard coded
> the path to see if that solved the problem, and the difference between
> the env lookup
> code and the hard coded path was almost the same, but substantially slower than
> the native file system.

And where exactly as the performance problem?

Anyway, if you submit your filesystem also provide a decent use case for it. :-)

Thanks,
//richard