Re: client-facing feature bits and pending kernel changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Jan 30, 2016 at 12:09 AM, Sage Weil <sweil@xxxxxxxxxx> wrote:
> Hi Zheng,
>
> We have one feature already merged to ceph.git, CRUSH_TUNABLES5, that's a
> pretty trivial change to crush/mapper.c that we can add to the kernel.
>
> But there are two more coming:
>
> OSDOPREPLY_ENCODING makes a small change to the OSDOpReply encoding for
> performance reasons.  Here is the PR
>
>         https://github.com/ceph/ceph/pull/7386
>
> The other is the file layout changes, which are much more invovled:
>
>         https://github.com/ceph/ceph/pull/7098

Can we avoid changing how file layout is encoded in MClientCaps and
MClientReply? Instead, we encode the namespace information at the end
of MClientCaps/MClientReply message. (like how we added inline data
related fields to these message).

Regards
Yan, Zheng

>
> Ideally we'd use the same feature bit for all of these, but it means they
> all need to upstream into Linux together.  Do you see a problem with that?
> Assuming we get it all ready to go before the next merge window..
>
> The tricky bit is we really need to know that we'll be able to do it
> together before we cut jewel too and commit to the overlapping feature
> bits.
>
> sage
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux