From: James Page <james.page@ubuntu.com>
To: Chaitanya Huilgol <Chaitanya.Huilgol@sandisk.com>,
Somnath Roy <Somnath.Roy@sandisk.com>,
Sage Weil <sage@newdream.net>,
"ceph-maintainers@ceph.com" <ceph-maintainers@ceph.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: tcmalloc issue
Date: Thu, 09 Apr 2015 15:13:20 +0100 [thread overview]
Message-ID: <55268900.1090909@ubuntu.com> (raw)
In-Reply-To: <9E914F5BD7F48A4782456CEB550A422824489892@SACMBXIP01.sdcorp.global.sandisk.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Thanks Chaitanya
I've tested and uploaded the patched version to trusty-proposed - the
SRU team should accept that into testing in the next day or so - they
will update the bug when that happens.
On 09/04/15 10:00, Chaitanya Huilgol wrote:
> Hi James,
>
> Please find source of the test program to verify this bug at
> http://pastebin.com/KAxQZARm compile it with -ltcmalloc To test:
> Export a non-default value of the cache size, for eg # export
> TCMALLOC_MAX_TOTAL_THREAD_CACHE_BYTES=67108864 Run the test prog,
> For the buggy version you will see
>
> Tcmalloc BUG! TCMALLOC_MAX_TOTAL_THREAD_CACHE_BYTES: 67108864
> Internal Size: 33554432 different
>
> With the bug fixed, you should see
>
> "Tcmalloc Internal and Env cache size are same:67108864"
>
> Hope this helps.
>
> Regards, Chaitanya
>
> -----Original Message----- From: ceph-devel-owner@vger.kernel.org
> [mailto:ceph-devel-owner@vger.kernel.org] On Behalf Of James Page
> Sent: Thursday, April 09, 2015 11:29 AM To: Somnath Roy; Sage Weil;
> ceph-maintainers@ceph.com Cc: ceph-devel@vger.kernel.org Subject:
> Re: tcmalloc issue
>
> On 01/04/15 18:54, Somnath Roy wrote:
>> the tcmalloc bug is reported in the following link.
>
>> http://code.google.com/p/gperftools/issues/detail?id=585
>
>> So, do you want us to give the steps on how we are hitting the
>> following trace or to reproduce the bug reported in the above
>> link ?
>
>> If you are asking about hitting the stack trace I mentioned
>> below, it is just running ceph with lot of IOs for longer period
>> of time.
>
> A minimal test case on how to reproduce the bug is sufficient; we
> can of course complete the second activity as well as soon as we
> have the update available.
>
> Cheers
>
> James
>
>
> -- 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
>
> ________________________________
>
> PLEASE NOTE: The information contained in this electronic mail
> message is intended only for the use of the designated recipient(s)
> named above. If the reader of this message is not the intended
> recipient, you are 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) immediately and destroy any
> and all copies of this message in your possession (whether hard
> copies or electronically stored copies).
>
- --
James Page
Ubuntu and Debian Developer
james.page@ubuntu.com
jamespage@debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVJokAAAoJEL/srsug59jDnNsQAM1h8T+XbzbyxIk31MSGuh6h
TfFs4ioBmv6IJFn7E+Le3WES3/Yqmhy1Sf1AHr1QtQNARJ9qqmNuU+M7IA/84A6o
6VvxKBb3fHWGJieG/ymaVVREuJUHJLfEEaqyZOrh++nsyuzf/nAymKSzJMl5Z8o1
ugOSqS/GryXORW2nzuWIHeAh3feETyBe2rFBeYTYkR65fsFyjMK5DTHNLh0SFTR3
Elc+qdyamau+XwlRZOz9ClyELk0vP2iWsaNj/KJrXGm104aCaf2NhnsX4IW4yz1s
GkcPhaFtR/V9d/txS8syMmh9b01rQL6Zxje3n0C63E0/AqLqBHF7NX60xbeiqAvw
5xPTK/6e4dARPaIzzCgY4vEjX/CQ38kFQYikU6lSIww873LgtdPAzJp15axH40E4
1YdtMAoSva/hVwkkjPLK7a8SVg4+sfVOho4FH7m8TZmLxpMXSH+ea4SFN9s9uuEa
jnA3mo5T50EeXQuYvmO87A4ABKGrOwBOvr3rmF4q/GnHGdONI+fctQW7JSmjJsMH
WrOwAWyte+A5hRRySiPw7EXqrj583l/iTaP+pd0eyWTcpoKKxp3Ver2nIsWGEe7+
Mq1lFii8Z3Z4rqthjWEg4iVw3HwQS+ArjYISuy4TnQUcnbG/Avp0liMM4VaBndF1
gefiZ4SMb5yxPriWndzf
=H69u
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-04-09 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 23:18 tcmalloc issue Somnath Roy
2015-03-26 23:47 ` Sage Weil
2015-03-30 17:36 ` Somnath Roy
2015-04-01 15:56 ` James Page
2015-04-01 17:54 ` Somnath Roy
2015-04-01 18:09 ` Alexandre DERUMIER
2015-04-09 5:59 ` James Page
2015-04-09 9:00 ` Chaitanya Huilgol
2015-04-09 14:13 ` James Page [this message]
2015-04-16 11:48 ` James Page
2015-04-16 14:55 ` Somnath Roy
2015-03-26 23:53 ` Mark Nelson
2015-03-27 7:21 ` Alexandre DERUMIER
2015-03-27 9:53 ` Chaitanya Huilgol
2015-03-27 14:37 ` Alexandre DERUMIER
2015-03-27 14:26 ` Chaitanya Huilgol
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=55268900.1090909@ubuntu.com \
--to=james.page@ubuntu.com \
--cc=Chaitanya.Huilgol@sandisk.com \
--cc=Somnath.Roy@sandisk.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-maintainers@ceph.com \
--cc=sage@newdream.net \
/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.