From: Eric Van Hensbergen <ericvh@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH]: v9fs: add readpage support
Date: Fri, 13 Jan 2006 16:27:14 -0600 [thread overview]
Message-ID: <a4e6962a0601131427m4fc2f88p74da20cdc2fd7fe@mail.gmail.com> (raw)
In-Reply-To: <20060113141445.14b6469a.akpm@osdl.org>
On 1/13/06, Andrew Morton <akpm@osdl.org> wrote:
> Eric Van Hensbergen <ericvh@gmail.com> wrote:
> >
> > I went looking for an example of how to do this better. More or less,
> > v9fs reads and writes are similar to DirectIO since they don't go
> > through the page-cache.
>
> hm. Why not?
>
At the moment we'd rather not cache anything with v9fs as it hides
operations from the servers, and in the case of synthetic servers it
can be a bad thing. There is a somewhat well-understood strategy for
how to do cacheing of static files in a sane manner under 9P, but we
were holding off on trying to move that into v9fs for the time being.
The only reason we added the read-only mmap support back in was to
support users who were trying to access executables over 9P
connections.
> >
> > Now, that being said, it still seems to me to be a bit heavy weight --
> > do folks have a better pointer to code that I can use as an example of
> > how to do this more efficiently?
>
> Not really. If that's what you need to do then that's the way to do it.
> We've had nasty races and other problems wrt invalidate_inode_pages2 and
> pagefaults, so I suggest you test that mix carefully.
>
> Have you tried fsx-linux? It's really good for finding data integrity
> bugs. There's a copy in
> http://www.zip.com.au/~akpm/linux/patches/stuff/ext3-tools.tar.gz.
>
We've been regression testing with vanilla fsx, I'll upgrade to
fsx-linux and make sure we are clean.
>
> I'd suggest that you want the mapping->nrpages test - it'll be a useful
> speedup in the common case.
>
Yeah, as I was tracing through the invalidate_inode_pages2() this
morning I realized this is probably a good idea. Should have a new
patch to you by the end of the weekend.
-eric
prev parent reply other threads:[~2006-01-13 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 1:14 [PATCH]: v9fs: add readpage support Eric Van Hensbergen
2006-01-11 11:38 ` Andrew Morton
2006-01-11 13:05 ` Eric Van Hensbergen
2006-01-13 21:45 ` Eric Van Hensbergen
2006-01-13 22:14 ` Andrew Morton
2006-01-13 22:27 ` Eric Van Hensbergen [this message]
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=a4e6962a0601131427m4fc2f88p74da20cdc2fd7fe@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.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