From: Jeff Layton <jlayton@redhat.com>
To: Daniel Gryniewicz <dang@redhat.com>
Cc: "samba-technical@lists.samba.org"
<samba-technical@lists.samba.org>,
Ganesha NFS List <nfs-ganesha-devel@lists.sourceforge.net>,
David Howells <dhowells@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: new statx() like interface for libcephfs
Date: Tue, 28 Jun 2016 15:05:24 -0400 [thread overview]
Message-ID: <1467140724.32374.32.camel@redhat.com> (raw)
In-Reply-To: <CAL-2WbF5HAoAvbje8xr91OP5Cd1ye7UF7W+PA01m-V1+O==DjA@mail.gmail.com>
On Tue, 2016-06-28 at 14:53 -0400, Daniel Gryniewicz wrote:
> Is stx_version a generation ID for the inode that can be used for the
> NFSv4 Change ID? If so, that would be quite useful to us. Otherwise,
> I'm not sure there's that much in there that's useful beyond what stat
> already provides, unless I'm missing something.
>
Yeah, I think that's the idea behind that field in statx calls, but
I'll note that I didn't wire that up here. That is the nice thing about
the proposed statx API though. We can add stuff like that in a
piecemeal fashion, as long as the callers check the stx_mask to make
sure the returned values are legit.
I'll look at whether it's possible to wire that up as well if it's
helpful for ganesha.
> On Tue, Jun 28, 2016 at 2:17 PM, Jeff Layton <jlayton@redhat.com> wrote:
> >
> > I have a patchset queued up for ceph that adds btime (birthtime)
> > support to it. What was lacking though was a mechanism to get the btime
> > out of the inode.
> >
> > Rather than cook up a brand new interface just for the btime, I decided
> > to "borrow" the work that David Howells did with the new proposed
> > statx() interface. The pull request to add this to ceph is up here:
> >
> > https://github.com/ceph/ceph/pull/9965
> >
> > Sage has already closed it out which I take to mean that he has pulled
> > the patches into a staging branch for eventual merge.
> >
> > It occurs to me though that I didn't ask anyone who is working on the
> > samba vfs or ganesha fsal code whether they think this interface is
> > acceptable.
> >
> > Since Samba and Ganesha are the targeted users of this interface, it'd
> > be good to have developers from both communities take a look and see if
> > there are any problems here.
> >
> > Does anyone see any issues with the above pull request?
> > --
> > Jeff Layton <jlayton@redhat.com>
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jeff Layton <jlayton@redhat.com>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" 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:[~2016-06-28 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 18:17 new statx() like interface for libcephfs Jeff Layton
2016-06-28 18:53 ` Daniel Gryniewicz
2016-06-28 19:05 ` Jeff Layton [this message]
[not found] ` <CAL-2WbF5HAoAvbje8xr91OP5Cd1ye7UF7W+PA01m-V1+O==DjA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-28 20:47 ` Frank Filz
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=1467140724.32374.32.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dang@redhat.com \
--cc=dhowells@redhat.com \
--cc=nfs-ganesha-devel@lists.sourceforge.net \
--cc=samba-technical@lists.samba.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.