All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylvain Munaut <s.munaut@whatever-company.com>
To: Dave Spano <dspano@optogenics.com>
Cc: "Sébastien Han" <han.sebastien@gmail.com>,
	ceph-devel <ceph-devel@vger.kernel.org>,
	"Sage Weil" <sage@inktank.com>
Subject: Re: [0.48.3] OSD memory leak when scrubbing
Date: Thu, 31 Jan 2013 16:26:26 +0100	[thread overview]
Message-ID: <CAF6-1L7cQ7TSngZG7T5+4168TUVs3ynOCcb2xpOsNadCFmxAew@mail.gmail.com> (raw)
In-Reply-To: <31226757.422.1359645742478.JavaMail.dspano@it1>

Hi,

> I'm crossing my fingers, but I just noticed that since I upgraded to kernel
> version 3.2.0-36-generic on Ubuntu 12.04 the other day, ceph-osd memory
> usage has stayed stable.

Unfortunately for me, I'm already on 3.2.0-36-generic  (Ubuntu 12.04 as well).

Cheers,

    Sylvain


PS: Dave sorry for the double, I forgot reply-to-all ...

  parent reply	other threads:[~2013-01-31 15:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 20:01 [0.48.3] OSD memory leak when scrubbing Sylvain Munaut
2013-01-22 21:19 ` Sébastien Han
2013-01-22 21:32   ` Sylvain Munaut
2013-01-22 21:38     ` Sébastien Han
2013-01-25 16:29       ` Sébastien Han
2013-01-25 20:16         ` Sylvain Munaut
2013-01-27 16:17           ` Sylvain Munaut
2013-01-27 17:47             ` Sage Weil
2013-01-27 18:17               ` Sylvain Munaut
2013-01-30  9:12               ` Sylvain Munaut
2013-01-30  9:18                 ` Sage Weil
2013-01-30 13:26                   ` Sylvain Munaut
2013-01-30 19:40                     ` Sage Weil
2013-01-31 13:20                       ` Sylvain Munaut
     [not found]                         ` <31226757.422.1359645742478.JavaMail.dspano@it1>
2013-01-31 15:26                           ` Sylvain Munaut [this message]
2013-01-31 19:57                         ` Sage Weil
2013-02-03 18:17                           ` Loic Dachary
     [not found]                             ` <CAOLwVUkUFvLihb6KbxG9Et7R_-ZTZpLQJYTjXm9TEe40V_ZRHg@mail.gmail.com>
2013-02-03 21:03                               ` Sébastien Han
2013-02-04 17:29                                 ` Sébastien Han
2013-02-04 19:29                                   ` Sage Weil
2013-02-04 21:03                                     ` Dan Mick
2013-02-04 21:08                                       ` Sébastien Han
2013-02-04 21:22                                         ` Gregory Farnum
2013-02-04 21:27                                           ` Sébastien Han
2013-02-16  7:09                                             ` Andrey Korolyov
2013-02-16  9:09                                               ` Wido den Hollander
2013-02-17 17:21                                                 ` Sébastien Han
2013-02-18 16:46                                                 ` 0.56 scrub OSD memleaks, WAS " Christopher Kunz
2013-02-19 19:23                                                   ` Samuel Just
2013-02-19 19:50                                                     ` Christopher Kunz

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=CAF6-1L7cQ7TSngZG7T5+4168TUVs3ynOCcb2xpOsNadCFmxAew@mail.gmail.com \
    --to=s.munaut@whatever-company.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dspano@optogenics.com \
    --cc=han.sebastien@gmail.com \
    --cc=sage@inktank.com \
    /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.