From: Sage Weil <sage@inktank.com>
To: David Howells <dhowells@redhat.com>
Cc: Milosz Tanski <milosz@adfin.com>,
ceph-devel@vger.kernel.org, zheng.z.yan@intel.com,
linux-cachefs@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCHv4 0/5] ceph: persistent caching with fscache
Date: Wed, 4 Sep 2013 09:25:35 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1309040923080.1073@cobra.newdream.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1309040851080.27503@cobra.newdream.net>
On Wed, 4 Sep 2013, Sage Weil wrote:
> Hi David!
>
> On Wed, 4 Sep 2013, David Howells wrote:
> > Sage Weil <sage@inktank.com> wrote:
> >
> > > David, are the fscache patches here ready for the next merge window? Do
> > > you have a preference for whose tree they go through?
> >
> > There's only one problem - patch 1 needs to come _after_ patch 2 to avoid
> > breaking git bisect. Plus these patches 2 and 4 extend the fscache API
> > without adjusting the documentation - but that can be added later.
> >
> > And I think Milosz deserves a beer (or other poison of his choice;-) for
> > finding a longstanding irritating bug.
> >
> > I think AFS, CIFS, NFS and 9P all need patching too, but I can attend to that.
> >
> > Should I take the patches through my tree? Then I can make the adjustments.
>
> Sure. Do you want the Ceph patches as well, or just the fscache bits?
> I'll repost the latest version, as it's gotten several fixes squashed in.
The full series is here:
git://github.com/ceph/ceph-client wip-fscache
https://github.com/ceph/ceph-client/commits/wip-fscache
Thanks!
sage
WARNING: multiple messages have this Message-ID (diff)
From: Sage Weil <sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
To: David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Milosz Tanski <milosz-B5zB6C1i6pkAvxtiuMwx3w@public.gmane.org>,
ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
zheng.z.yan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-cachefs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCHv4 0/5] ceph: persistent caching with fscache
Date: Wed, 4 Sep 2013 09:25:35 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1309040923080.1073@cobra.newdream.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1309040851080.27503-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
On Wed, 4 Sep 2013, Sage Weil wrote:
> Hi David!
>
> On Wed, 4 Sep 2013, David Howells wrote:
> > Sage Weil <sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org> wrote:
> >
> > > David, are the fscache patches here ready for the next merge window? Do
> > > you have a preference for whose tree they go through?
> >
> > There's only one problem - patch 1 needs to come _after_ patch 2 to avoid
> > breaking git bisect. Plus these patches 2 and 4 extend the fscache API
> > without adjusting the documentation - but that can be added later.
> >
> > And I think Milosz deserves a beer (or other poison of his choice;-) for
> > finding a longstanding irritating bug.
> >
> > I think AFS, CIFS, NFS and 9P all need patching too, but I can attend to that.
> >
> > Should I take the patches through my tree? Then I can make the adjustments.
>
> Sure. Do you want the Ceph patches as well, or just the fscache bits?
> I'll repost the latest version, as it's gotten several fixes squashed in.
The full series is here:
git://github.com/ceph/ceph-client wip-fscache
https://github.com/ceph/ceph-client/commits/wip-fscache
Thanks!
sage
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-09-04 16:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 21:26 [PATCHv4 0/5] ceph: persistent caching with fscache Milosz Tanski
2013-08-21 21:29 ` [PATCH 1/5] new cachefiles interface to check cache consistency Hongyi Jia
2013-08-21 21:29 ` [PATCH 2/5] new fscache " Hongyi Jia
2013-08-21 21:29 ` [PATCH 3/5] ceph: use fscache as a local presisent cache Milosz Tanski
2013-08-21 21:29 ` Milosz Tanski
2013-08-27 1:05 ` Sage Weil
2013-08-21 21:30 ` [PATCH 4/5] fscache: netfs function for cleanup post readpages Milosz Tanski
2013-09-03 17:24 ` Milosz Tanski
2013-08-21 21:30 ` [PATCH 5/5] ceph: clean PgPrivate2 on returning from readpages Milosz Tanski
2013-08-22 5:05 ` [PATCHv4 0/5] ceph: persistent caching with fscache Sage Weil
2013-08-22 5:05 ` Sage Weil
2013-08-22 12:58 ` Milosz Tanski
2013-08-22 12:58 ` Milosz Tanski
2013-09-04 15:49 ` David Howells
2013-09-04 15:49 ` David Howells
2013-09-04 15:54 ` Sage Weil
2013-09-04 15:54 ` Sage Weil
2013-09-04 16:25 ` Sage Weil [this message]
2013-09-04 16:25 ` Sage Weil
2013-09-05 12:34 ` David Howells
2013-09-04 16:24 ` [PATCH 2/5] new fscache interface to check cache consistency David Howells
2013-09-04 16:24 ` David Howells
2013-09-04 16:48 ` Milosz Tanski
2013-09-04 17:26 ` David Howells
2013-09-04 17:26 ` David Howells
2013-09-04 18:04 ` Milosz Tanski
2013-09-04 18:13 ` David Howells
2013-09-04 18:13 ` David Howells
2013-09-04 19:41 ` Milosz Tanski
2013-09-04 22:02 ` Milosz Tanski
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=alpine.DEB.2.00.1309040923080.1073@cobra.newdream.net \
--to=sage@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=milosz@adfin.com \
--cc=zheng.z.yan@intel.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 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.