From: James Page <james.page@ubuntu.com>
To: 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 06:59:04 +0100 [thread overview]
Message-ID: <55261528.7040607@ubuntu.com> (raw)
In-Reply-To: <755F6B91B3BE364F9BCA11EA3F9E0C6F28CB8270@SACMBXIP01.sdcorp.global.sandisk.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
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
- --
James Page
Ubuntu and Debian Developer
james.page@ubuntu.com
jamespage@debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVJhUoAAoJEL/srsug59jD/WoQAJqZYJ82xcDDxuD5C9RnUXha
2UtYNXZTK9O1NdiLqsNw14SPKtOQ6IDyfJjvB2v+ddfvRxhlfSM6LmC4ERa0t0SW
a3tfwx9fQ0WEz2r35nkupHwo+Z4yfTAuHgGom3rH6tq4gbAInn7J+4unsxghV1kf
op/c9qNJZV9jqfqMZFFgwwptK7rJ4mKJDvGIRU4ddc9HEKnqukJHQAHh3zUlNXC9
6y11RAHFh0FcgEEHys3o/ui0JVzNjmP8HJXISzyWSqO6J2NxqRNYoKGTk81zBvrf
IkWDDujCcTQoAU2aW6ERRvG1Dkzc9oTLdcmb0gGCKKpqa1m1GjnqS1B39rjheXio
HK5L9HO11Fs+9uONBXWvI6P0GXi3UQoe1NaVQB85EL+NPFbTdKr9zw8nOyyqZ9Y5
X55uVRAscLV/jb1vYIU5JxSNWof4BtPSjQzq29cithPqfWyF2N+eyQbCrAaIu1oP
QGSnryCsoWDARyvjMIFxcsd2X6nFnOd9DMgumi6O1ksKAe1P38k1iUWFwXXutby6
6eTdZtOj9Wc4VNRPb8SYBkBSlU+dCgRVMlNUImcCKWR6w8+Y9BbQU7OwQGEzj9Xw
f9sdi+4JA04l/BXdAtlVwSj4uSm2Q6R/YK4szpRGs24EOV6dX+aCMK5ezBIliPo0
D/7ZD03rXkiBzHuBqiay
=066U
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-04-09 5:59 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 [this message]
2015-04-09 9:00 ` Chaitanya Huilgol
2015-04-09 14:13 ` James Page
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=55261528.7040607@ubuntu.com \
--to=james.page@ubuntu.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.