From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Speed of 9pfuse on Linux
Date: Fri, 12 Feb 2010 06:45:34 -0600 [thread overview]
Message-ID: <A3A171B8-4405-40BE-A775-A34A42DF4E09@gmail.com> (raw)
In-Reply-To: <28dd59bb-f238-4f80-8b29-3863e91184d7@o28g2000yqh.googlegroups.com>
A few "solutions" exist:
Use Op instead - of course there is no Op exporter from sources or
Linux client -- but these could be rectified with work.
If used v9fs run with cache=loose or cache=fscache both of which
enables caching meta-data.
Convince the Linux community to fix ls - I think the kernel supports
Plan 9 style dirread now (there were some bug reports against v9fs
suggesting a plan 9 style dirread was possible) but tools haven't yet
been updated.
Submit a patch to 9pfuse and/or v9fs providing optional (mount time)
1s cache on metadata.
-Eric
Sent from my iPhone
On Feb 12, 2010, at 12:15 PM, Pavel Klinkovsky <pavel.klinkovsky@gmail.com
> wrote:
>> this is not surprising if you consider what's happening underneath:
> Clear.
>
> Understandable but very unpleasant.
>
> Pavel
>
next prev parent reply other threads:[~2010-02-12 12:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 9:27 Pavel Klinkovsky
2010-02-10 9:54 ` Gorka Guardiola
2010-02-10 12:28 ` Eric Van Hensbergen
2010-02-10 13:32 ` Pavel Klinkovsky
2010-02-10 11:57 ` Pavel Klinkovsky
2010-02-10 13:04 ` Eric Van Hensbergen
2010-02-10 12:09 ` maht
2010-02-10 13:32 ` Pavel Klinkovsky
2010-02-10 16:28 ` Eric Van Hensbergen
2010-02-10 16:44 ` Steve Simon
2010-02-10 18:54 ` Venkatesh Srinivas
2010-02-10 19:46 ` Gorka Guardiola
2010-02-12 10:53 ` Pavel Klinkovsky
2010-02-12 8:20 ` Jacob Todd
2010-02-12 11:25 ` roger peppe
2010-02-12 12:15 ` Pavel Klinkovsky
2010-02-12 12:45 ` Eric Van Hensbergen [this message]
2010-02-12 17:51 ` Tim Newsham
2010-02-12 18:07 ` Abhishek Kulkarni
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=A3A171B8-4405-40BE-A775-A34A42DF4E09@gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).