From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: memory leak in <=3.11.6
Date: Wed, 30 Oct 2013 07:58:04 +0000 (UTC) [thread overview]
Message-ID: <pan$daeed$63ab09ce$f7cf614c$9dc4736d@cox.net> (raw)
In-Reply-To: o1t5ka-p7g.ln1@hurikhan77.spdns.de
Kai Krakow posted on Wed, 30 Oct 2013 00:30:26 +0100 as excerpted:
> For me it started late 3.9 if I remember right. But I'm pretty sure it
> startet with 3.10 which I mostly upgraded to for using skinny extents.
> While skinny extents has helped subjective performance a little bit I
> since experience the problem with ever increasing RAM usage - up to the
> point of 15 GB swap, full RAM, and almost none of it is used for
> caching.
That's an interesting point. I've been cautious about enabling skinny
extents as well, and haven't enabled them here. (Nothing major, just a
couple early reports that I expect have long been worked out by now, but
I decided giving them a few more kernel releases to mature was probably a
good idea.)
So it'd be interesting to see if there's a correlation between skinny
extents and the memory issues as well, as there seems to be between
qgroups and the memory issues.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-10-30 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 4:22 memory leak in <=3.11.6 Tomasz Chmielewski
2013-10-29 23:30 ` Kai Krakow
2013-10-30 7:58 ` Duncan [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-28 22:34 Kai Krakow
2013-10-29 3:24 ` Jérôme Poulin
2013-10-29 16:42 ` Duncan
2013-10-29 22:46 ` Jérôme Poulin
2013-10-30 1:55 ` Wang Shilong
2013-10-29 23:26 ` Kai Krakow
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='pan$daeed$63ab09ce$f7cf614c$9dc4736d@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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.