From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/3] xfs: buffer cache shrinker overhaul V2
Date: Mon, 29 Nov 2010 11:58:56 +1100 [thread overview]
Message-ID: <1290992339-20849-1-git-send-email-david@fromorbit.com> (raw)
This series adds a per-filesystem LRU to the buffer cache. When
combined with a shrinker per filesystem, this enables us to
prioritise reclaim of buffers under memory pressure. This solves the
current problem of page cache reclaim having no concept of what the
pages actually contain in deciding which pages to reclaim.
The LRU is lazily updated, meaning that we only access the LRU
lists and locks when the last reference to a buffer goes away. As a
result, there is no impact to the hot buffer lookup path and we are
not constantly moving buffers around in the LRU.
This series effectively means that the buffer cache can now be made
independent of the page cache as we now have our own optimised
buffer cache reclaim mechanisms.
Version 2:
- removed buffer lru addition during xfs_buf_find() as it is done
lazily on the last reference going away.
- removed buffer type additions and used the existing macro to just
set the reference value.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-11-29 1:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 0:58 Dave Chinner [this message]
2010-11-29 0:58 ` [PATCH 1/3] xfs: convert xfsbud shrinker to a per-buftarg shrinker Dave Chinner
2010-11-29 0:58 ` [PATCH 2/3] xfs: add a lru to the XFS buffer cache Dave Chinner
2010-11-29 13:07 ` Christoph Hellwig
2010-11-29 0:58 ` [PATCH 3/3] xfs: connect up buffer reclaim priority hooks Dave Chinner
2010-11-29 13:08 ` Christoph Hellwig
2010-11-29 12:56 ` [PATCH 0/3] xfs: buffer cache shrinker overhaul V2 Christoph Hellwig
2010-11-30 4:40 ` Dave Chinner
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=1290992339-20849-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox