From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Priebe - Profihost AG Subject: Re: trying to compile with-jemalloc but ceph-osd is still linked to libtcmalloc Date: Tue, 07 Jul 2015 14:46:18 +0200 Message-ID: <559BCA1A.5010503@profihost.ag> References: <5596529F.8060709@profihost.ag> <559B992E.4050005@profihost.ag> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mail-ph.de-nserver.de ([85.158.179.214]:43514 "EHLO mail-ph.de-nserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756857AbbGGMqV (ORCPT ); Tue, 7 Jul 2015 08:46:21 -0400 In-Reply-To: Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Shishir Gowda , "ceph-devel@vger.kernel.org" Am 07.07.2015 um 12:55 schrieb Shishir Gowda: > Hi Stefan, >=20 > I tried with hammer, and with google perf devel tools installed, and = still worked as expected. >=20 > You can check in .../ceph/src/ceph-osd directory to confirm if you ar= e checking with the right binaries. Strange under Debian Wheezy it always bind to tcmalloc. I've now remove= d googleperftools and it works fine. Stefan >=20 > With regards, > Shishir >=20 >> -----Original Message----- >> From: Stefan Priebe - Profihost AG [mailto:s.priebe@profihost.ag] >> Sent: Tuesday, July 07, 2015 2:48 PM >> To: Shishir Gowda; ceph-devel@vger.kernel.org >> Subject: Re: trying to compile with-jemalloc but ceph-osd is still l= inked to >> libtcmalloc >> >> >> Am 07.07.2015 um 09:56 schrieb Shishir Gowda: >>> Hi Stefan, >>> >>> I built it with ./configure --without-tcmalloc and --with-jemalloc,= and >> resulting binaries are not being linked with tcmalloc. >> >> It works for me if i remove the google perftools dev package. But if= it is >> installed hammer always builds against tcmalloc. >> >>> ldd src/ceph-osd >>> linux-vdso.so.1 =3D> (0x00007fff2a5fe000) >>> libjemalloc.so.1 =3D> /usr/lib/x86_64-linux-gnu/libjemalloc= =2Eso.1 >> (0x00007f99d1c7b000) >>> libaio.so.1 =3D> /lib/x86_64-linux-gnu/libaio.so.1 (0x00007= f99d1a79000) >>> libleveldb.so.1 =3D> /usr/lib/x86_64-linux-gnu/libleveldb.s= o.1 >> (0x00007f99d182b000) >>> liblttng-ust.so.0 =3D> /usr/lib/x86_64-linux-gnu/liblttng-u= st.so.0 >> (0x00007f99d15dc000) >>> libpthread.so.0 =3D> /lib/x86_64-linux-gnu/libpthread.so.0 >> (0x00007f99d13be000) >>> libcrypto++.so.9 =3D> /usr/lib/libcrypto++.so.9 (0x00007f99= d0cc1000) >>> libuuid.so.1 =3D> /lib/x86_64-linux-gnu/libuuid.so.1 >> (0x00007f99d0abc000) >>> libdl.so.2 =3D> /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f9= 9d08b8000) >>> libboost_thread.so.1.54.0 =3D> /usr/lib/x86_64-linux- >> gnu/libboost_thread.so.1.54.0 (0x00007f99d06a1000) >>> librt.so.1 =3D> /lib/x86_64-linux-gnu/librt.so.1 (0x00007f9= 9d0499000) >>> libboost_system.so.1.54.0 =3D> /usr/lib/x86_64-linux- >> gnu/libboost_system.so.1.54.0 (0x00007f99d0295000) >>> libstdc++.so.6 =3D> /usr/lib/x86_64-linux-gnu/libstdc++.so.= 6 >> (0x00007f99cff90000) >>> libm.so.6 =3D> /lib/x86_64-linux-gnu/libm.so.6 (0x00007f99c= fc8a000) >>> libgcc_s.so.1 =3D> /lib/x86_64-linux-gnu/libgcc_s.so.1 >> (0x00007f99cfa74000) >>> libc.so.6 =3D> /lib/x86_64-linux-gnu/libc.so.6 (0x00007f99c= f6ae000) >>> /lib64/ld-linux-x86-64.so.2 (0x00007f99d1ec2000) >>> libsnappy.so.1 =3D> /usr/lib/libsnappy.so.1 (0x00007f99cf4a= 8000) >>> liblttng-ust-tracepoint.so.0 =3D> /usr/lib/x86_64-linux-gnu= /liblttng-ust- >> tracepoint.so.0 (0x00007f99cf28e000) >>> liburcu-bp.so.2 =3D> /usr/lib/x86_64-linux-gnu/liburcu-bp.s= o.2 >> (0x00007f99cf086000) >>> liburcu-cds.so.2 =3D> /usr/lib/x86_64-linux-gnu/liburcu-cds= =2Eso.2 >>> (0x00007f99cee7f000) >>> >>> I tried it with upstream master, what branch are you using. >>> >>> With regards, >>> Shishir >>> >>>> -----Original Message----- >>>> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel- >>>> owner@vger.kernel.org] On Behalf Of Stefan Priebe >>>> Sent: Friday, July 03, 2015 2:45 PM >>>> To: ceph-devel@vger.kernel.org >>>> Subject: trying to compile with-jemalloc but ceph-osd is still lin= ked >>>> to libtcmalloc >>>> >>>> Hi, >>>> >>>> i'm trying to compile current hammer with-jemalloc. >>>> >>>> configure .. --without-tcmalloc --with-jemalloc >>>> >>>> but resulting ceph-osd is still linked against tcmalloc: >>>> ldd /usr/bin/ceph-osd >>>> linux-vdso.so.1 =3D> (0x00007fffbf3b9000) >>>> libjemalloc.so.1 =3D> >>>> /usr/lib/x86_64-linux-gnu/libjemalloc.so.1 >>>> (0x00007fc44bc25000) >>>> libaio.so.1 =3D> /lib/x86_64-linux-gnu/libaio.so.1 >>>> (0x00007fc44ba23000) >>>> libleveldb.so.1 =3D> /usr/lib/x86_64-linux-gnu/libleveldb= =2Eso.1 >>>> (0x00007fc44b7d2000) >>>> libpthread.so.0 =3D> /lib/x86_64-linux-gnu/libpthread.so.= 0 >>>> (0x00007fc44b5b6000) >>>> libcrypto++.so.9 =3D> /usr/lib/libcrypto++.so.9 (0x00007f= c44aea8000) >>>> libuuid.so.1 =3D> /lib/x86_64-linux-gnu/libuuid.so.1 >>>> (0x00007fc44aca2000) >>>> libdl.so.2 =3D> /lib/x86_64-linux-gnu/libdl.so.2 (0x00007= fc44aa9e000) >>>> libboost_thread.so.1.49.0 =3D> >>>> /usr/lib/libboost_thread.so.1.49.0 >>>> (0x00007fc44aa81000) >>>> librt.so.1 =3D> /lib/x86_64-linux-gnu/librt.so.1 (0x00007= fc44a878000) >>>> libstdc++.so.6 =3D> /usr/lib/x86_64-linux-gnu/libstdc++.s= o.6 >>>> (0x00007fc44a571000) >>>> libm.so.6 =3D> /lib/x86_64-linux-gnu/libm.so.6 (0x00007fc= 44a2ef000) >>>> libgcc_s.so.1 =3D> /lib/x86_64-linux-gnu/libgcc_s.so.1 >>>> (0x00007fc44a0d8000) >>>> libc.so.6 =3D> /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc= 449d4d000) >>>> /lib64/ld-linux-x86-64.so.2 (0x00007fc44be65000) >>>> libsnappy.so.1 =3D> /usr/lib/libsnappy.so.1 (0x00007fc449= b47000) >>>> libtcmalloc.so.4 =3D> /usr/lib/libtcmalloc.so.4 (0x00007f= c4498d4000) >>>> libunwind.so.7 =3D> /usr/lib/libunwind.so.7 >>>> (0x00007fc4496bb000) >>>> >>>> Stefan >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe ceph-dev= el" >>>> in the body of a message to majordomo@vger.kernel.org More >> majordomo >>>> info at http://vger.kernel.org/majordomo-info.html >>> >>> ________________________________ >>> >>> PLEASE NOTE: The information contained in this electronic mail mess= age is >> intended only for the use of the designated recipient(s) named above= =2E If >> the reader of this message is not the intended recipient, you are he= reby >> notified that you have received this message in error and that any r= eview, >> dissemination, distribution, or copying of this message is strictly = prohibited. >> If you have received this communication in error, please notify the = sender >> by telephone or e-mail (as shown above) immediately and destroy any = and >> all copies of this message in your possession (whether hard copies o= r >> electronically stored copies). >>> >=20 > ________________________________ >=20 > PLEASE NOTE: The information contained in this electronic mail messag= e is intended only for the use of the designated recipient(s) named abo= ve. If the reader of this message is not the intended recipient, you ar= e hereby notified that you have received this message in error and that= any review, dissemination, distribution, or copying of this message is= strictly prohibited. If you have received this communication in error,= please notify the sender by telephone or e-mail (as shown above) immed= iately and destroy any and all copies of this message in your possessio= n (whether hard copies or electronically stored copies). >=20 > N=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BDr=EF=BF=BD=EF=BF=BDy=EF= =BF=BD=EF=BF=BD=EF=BF=BDb=EF=BF=BDX=EF=BF=BD=EF=BF=BD=C7=A7v=EF=BF=BD^=EF= =BF=BD)=DE=BA{.n=EF=BF=BD+=EF=BF=BD=EF=BF=BD=EF=BF=BDz=EF=BF=BD]z=EF=BF= =BD=EF=BF=BD=EF=BF=BD{ay=EF=BF=BD=1D=CA=87=DA=99=EF=BF=BD,j=07=EF=BF=BD= =EF=BF=BDf=EF=BF=BD=EF=BF=BD=EF=BF=BDh=EF=BF=BD=EF=BF=BD=EF=BF=BDz=EF=BF= =BD=1E=EF=BF=BDw=EF=BF=BD=EF=BF=BD=EF=BF=BD=0C=EF=BF=BD=EF=BF=BD=EF=BF=BD= j:+v=EF=BF=BD=EF=BF=BD=EF=BF=BDw=EF=BF=BDj=EF=BF=BDm=EF=BF=BD=EF=BF=BD=EF= =BF=BD=EF=BF=BD=07=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BDzZ+=EF=BF=BD=EF=BF= =BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=DD=A2j"=EF=BF=BD=EF=BF=BD!tml=3D >=20 -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html