From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Thank you very much
Date: Thu, 12 Apr 2007 10:22:36 -0400 [thread overview]
Message-ID: <20070412142236.A4CBD1E8C1C@holo.morphisms.net> (raw)
In-Reply-To: <461D191C.1070606@tecmav.com>
> Let me issue another question.
>
> Beeing constrained to mount small file server on FreeBSD-p9p the high
> number (up to 8630) of cached fids can be a problem.
>
> Is it configurable ?
You're actually mounting the file system as a
FUSE file system, via the 9pfuse protocol converter.
The problem here is that the FreeBSD FUSE kernel
module is not issuing FUSE_FORGET (like Tclunk)
messages as aggressively as it could.
On Linux, if FUSE walks the same path twice and gets
different nodeids (like fids), then it tosses away one of
them -- no point caching them both -- but FreeBSD
appears to keeps them both in the cache.
You'd have to ask the fuse4bsd guys about this behavior.
Russ
next prev parent reply other threads:[~2007-04-12 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 17:21 Adriano Verardo
2007-04-12 14:22 ` Russ Cox [this message]
2007-04-12 16:45 ` Jack Johnson
2007-04-12 17:18 ` Russ Cox
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=20070412142236.A4CBD1E8C1C@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).