From: Ken Dreyer <kdreyer@redhat.com>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: reconciliation between firefly and v0.80.8.2
Date: Fri, 24 Jul 2015 11:43:44 -0600 [thread overview]
Message-ID: <55B27950.9070409@redhat.com> (raw)
In-Reply-To: <55B2708B.1020705@dachary.org>
On 07/24/2015 11:06 AM, Loic Dachary wrote:
> * build: remove LIBPERFGLUE from LIBMDS
> is unique to v0.80.8.2 and it is unclear why it was found to be usefu in
> isolation. An issue for firefly backport of
> http://tracker.ceph.com/issues/10691 was open at
> http://tracker.ceph.com/issues/12461#note-1
Yeah, to shed more light why we found that patch to be important downstream:
The RHEL product has strict requirements about support, stability, ABI
guarantees, etc. Our team's able to support the gperftools-libs package
for the Ceph product, but not for all of RHEL. Since
/usr/bin/ceph-dencoder was only thing in ceph-common that links again
libtcmalloc, if we could fix the over-linking there, then we avoid the
whole issue.
The downstream BZ that corresponds to that ceph.com Redmine ticket is
https://bugzilla.redhat.com/1186953 in case anyone's interested.
- Ken
prev parent reply other threads:[~2015-07-24 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 17:06 reconciliation between firefly and v0.80.8.2 Loic Dachary
2015-07-24 17:20 ` Loic Dachary
2015-07-24 17:43 ` Ken Dreyer [this message]
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=55B27950.9070409@redhat.com \
--to=kdreyer@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.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.