All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: Sage Weil <sweil@redhat.com>,
	zyan@redhat.com, ceph-devel@vger.kernel.org
Subject: Re: btime and change_attr features in kclient
Date: Mon, 24 Oct 2016 12:25:43 -0400	[thread overview]
Message-ID: <1477326343.14828.11.camel@redhat.com> (raw)
In-Reply-To: <1477325965.14828.8.camel@redhat.com>

On Mon, 2016-10-24 at 12:19 -0400, Jeff Layton wrote:
> On Mon, 2016-10-24 at 16:16 +0000, Sage Weil wrote:
> > 
> > Hi,
> > 
> > This PR that changes the entity_addr encoding is finally ready to merge
> > 
> >         https://github.com/ceph/ceph/pull/9825
> > 
> > but it defines an MSG_ADDR2 feature bit indicating whether we support the 
> > new addr encoding.  Right now it's defined with the same value as the 
> > FS_CHANGE_ATTR and FS_BTIME feature bit.  Are those upstream yet?  If not, 
> > we should get the addr2 support in at the same time so that we can 
> > conserve a feature bit.  If not, we'll have to consume another bit.  :(
> > 
> > sage
> > 
> 
> That support is merged into master -- is that what you mean by
> "upstream"?
> 

Sorry, I misread the subject...

No, those are not yet supported or recognized in kclient yet. In which
kernel are you planning to merge the addr2 patches?
-- 
Jeff Layton <jlayton@redhat.com>

  reply	other threads:[~2016-10-24 16:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 16:16 btime and change_attr features in kclient Sage Weil
2016-10-24 16:19 ` Jeff Layton
2016-10-24 16:25   ` Jeff Layton [this message]
2016-10-24 16:28     ` Sage Weil
2016-10-24 16:30       ` Jeff Layton
2016-10-24 16:26   ` Sage Weil

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=1477326343.14828.11.camel@redhat.com \
    --to=jlayton@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sweil@redhat.com \
    --cc=zyan@redhat.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.