All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milosz Tanski <milosz@adfin.com>
To: David Howells <dhowells@redhat.com>
Cc: "linux-cachefs@redhat.com" <linux-cachefs@redhat.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: FSCache: Cookie create and destroy semantics on file open
Date: Wed, 7 Aug 2013 08:08:28 -0400	[thread overview]
Message-ID: <4307898982697141463@unknownmsgid> (raw)
In-Reply-To: <26386.1375855465@warthog.procyon.org.uk>

Can you share those patches? I'd like to know what the approach you've
taken since I'm trying to figure out how to solve it for Ceph.

- M

On Aug 7, 2013, at 2:04 AM, David Howells <dhowells@redhat.com> wrote:

> Milosz Tanski <milosz@adfin.com> wrote:
>
>> I have a question for you about how added / removing the cookie for a
>> NFS inode works. Right the cache entry gets added when the file is
>> open. It gets revoked when the file re-opened in write mode. What
>> happens in this case.
>>
>> Open for read (create cookie) -> Open for write (destroy cookie) ->
>> Open for read (create cookie again)
>>
>> In this case, none of the 3 files were closed.
>
> No.  The way NFS is doing this is wrong.  I have been given some patches that
> should fix this, I think.
>
> David

  reply	other threads:[~2013-08-07 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07  4:40 FSCache: Cookie create and destroy semantics on file open Milosz Tanski
2013-08-07  6:04 ` David Howells
2013-08-07 12:08   ` Milosz Tanski [this message]
2013-08-07 12:46     ` David Howells

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=4307898982697141463@unknownmsgid \
    --to=milosz@adfin.com \
    --cc=dhowells@redhat.com \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-fsdevel@vger.kernel.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.