From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Pavel Shilovsky <piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Shirish Pargaonkar
<shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: revalidate inode before generic_file_aio_read
Date: Thu, 10 Mar 2011 15:44:14 +0530 [thread overview]
Message-ID: <4D78A476.7050800@suse.de> (raw)
In-Reply-To: <AANLkTinfzBXvfNmerWHoMuZ8NkeZLJxNE=MJYcFhA8Nu-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 03/10/2011 02:02 PM, Pavel Shilovsky wrote:
> Hi all!
>
> As soon as we have tunable actimeo, I think we should revalidate inode
> all the time we want to read from it, like NFS does it.
Did you mean while using strict cache along with actimeo? Conceptually
one should not be needing to use them together, right?
> What do you think about it? If it's ok, I am ready to provide a patch for this.
>
--
Suresh Jayaraman
next prev parent reply other threads:[~2011-03-10 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 8:32 revalidate inode before generic_file_aio_read Pavel Shilovsky
[not found] ` <AANLkTinfzBXvfNmerWHoMuZ8NkeZLJxNE=MJYcFhA8Nu-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-10 10:14 ` Suresh Jayaraman [this message]
[not found] ` <4D78A476.7050800-l3A5Bk7waGM@public.gmane.org>
2011-03-10 10:33 ` Pavel Shilovsky
[not found] ` <AANLkTinVkxs9vO9QP_BdmFfRcK5duVWviFAbgg6NoSHw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-10 20:49 ` Jeff Layton
[not found] ` <20110310154933.1fa017a0-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org>
2011-03-11 9:01 ` Pavel Shilovsky
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=4D78A476.7050800@suse.de \
--to=sjayaraman-l3a5bk7wagm@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.