From: Csaba Henk <csaba@gluster.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: avati@gluster.com, muirj@nortel.com,
fuse-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, dl-hacking@gluster.com
Subject: Re: [PATCH] fuse: cache invalidation calls
Date: Thu, 4 Jun 2009 11:32:32 +0200 [thread overview]
Message-ID: <100d90a90906040232ofd2b5ebw8c8d5f677b13e840@mail.gmail.com> (raw)
In-Reply-To: <E1MC99F-0004l5-JF@pomaz-ex.szeredi.hu>
On Thu, Jun 4, 2009 at 11:22 AM, Miklos Szeredi <miklos@szeredi.hu> wrote:
> On Wed, 3 Jun 2009, Anand Avati wrote:
>> I was wondering how the userland libfuse would be made aware of the
>> presence of these two notification features?
>
> Here's a patch against fuse CVS. It's also from John Muir.
In fact, what we were meditating about is the lack of the
FUSE_KERNEL_MINOR_VERSION bump. Without that, how do the two parties
negotiate if the rev inval messages are understood? One of John's
patches in his patchset had it bumped though...
Csaba
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-04 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <683929306.1044151244033426071.JavaMail.root@mb1>
2009-06-03 12:51 ` [PATCH] fuse: cache invalidation calls Anand Avati
2009-06-04 9:22 ` Miklos Szeredi
2009-06-04 9:32 ` Csaba Henk [this message]
2009-06-04 9:35 ` Miklos Szeredi
2009-06-03 8:01 Miklos Szeredi
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=100d90a90906040232ofd2b5ebw8c8d5f677b13e840@mail.gmail.com \
--to=csaba@gluster.com \
--cc=avati@gluster.com \
--cc=dl-hacking@gluster.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=muirj@nortel.com \
/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).