From: Martin Waitz <tali@admingilde.org>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: making an in-memory hashing table ["name" -> ino_t] with thousands of entries
Date: Fri, 1 Oct 2004 14:30:19 +0200 [thread overview]
Message-ID: <20041001123019.GC4072@admingilde.org> (raw)
In-Reply-To: <20041001120222.GA8507@lkcl.net>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
hi :)
On Fri, Oct 01, 2004 at 01:02:22PM +0100, Luke Kenneth Casson Leighton wrote:
> bearing in mind that for every file accessed via a fuse
> filesystem, a cache entry is created, and therefore the number
> of entries could potentially run into hundreds of thousands
> of entries.
but these can be cleaned if needed.
why do you have to move all inodes into the kernel when the kernel
already cache those that are really needed?
(perhaps I'm misunderstandig fuses role here)
--
Martin Waitz
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-01 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 12:02 making an in-memory hashing table ["name" -> ino_t] with thousands of entries Luke Kenneth Casson Leighton
2004-10-01 12:30 ` Martin Waitz [this message]
2004-10-01 13:33 ` Luke Kenneth Casson Leighton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041001123019.GC4072@admingilde.org \
--to=tali@admingilde.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcl@lkcl.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox