From: Don Porter <porterde@cs.utexas.edu>
To: Theodore Tso <tytso@mit.edu>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: ext3 leaking buffer_heads
Date: Wed, 25 Mar 2009 02:04:25 -0500 [thread overview]
Message-ID: <49C9D779.4030805@cs.utexas.edu> (raw)
In-Reply-To: <20090325004609.GF32307@mit.edu>
Theodore Tso wrote:
> The journal is a fixed sized, circular log, so the buffer_head will be
> reused eventually. In the case of memory pressure the unreferenced
> buffer_head will be freed, but since we never reference the contents
> of the journal, we could be more aggressive about freeing the
> buffer_head just to avoid pushing out more valuable memory contents
> when we start getting put under memory pressure.
>
> - Ted
>
Thanks Ted. This makes sense.
I am working on a research project that may require more aggressive
reclaiming of these buffer_heads. If I were to implement something,
would this be an optimization the maintainers would be interested in?
Thanks again for the help,
Don
prev parent reply other threads:[~2009-03-25 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 19:56 ext3 leaking buffer_heads Don Porter
2009-03-23 22:00 ` Eric Sandeen
2009-03-24 22:43 ` Don Porter
2009-03-25 0:46 ` Theodore Tso
2009-03-25 7:04 ` Don Porter [this message]
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=49C9D779.4030805@cs.utexas.edu \
--to=porterde@cs.utexas.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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.