From: Alex Elsayed <eternaleye-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Bcache data layout - suited as swap filesystem on SSDs?
Date: Fri, 08 Mar 2013 22:52:02 -0800 [thread overview]
Message-ID: <khem6g$avh$1@ger.gmane.org> (raw)
I came across a paper [1] today talking about improving the Linux swap
system for use on SSDs, and I realized that some points made in the paper
could be addressed by using bcache 'in reverse', where instead of caching a
slower block device it stores pages on behalf of faster memory.
Bcache already optimizes for SSDs by writing linearly where possible, using
'buckets' sized to work well with eraseblocks, and taking advantage of high
random read performance.
The paper advocates doing much the same with swap on SSDs, although it also
talks about removing layers of software between the VM and the SSD.
Since bcache is an efficient way of storing sparse, fixed-size chunks of
data identified by addresses, it might be a really interesting data layout
for efficient swap on SSDs.
[1] http://pages.cs.wisc.edu/~msaxena/FlashVMpaper.html
reply other threads:[~2013-03-09 6:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='khem6g$avh$1@ger.gmane.org' \
--to=eternaleye-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox