From: Shaohua Li <shli@kernel.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: shli@fusionio.com, linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC]swap improvements for fast SSD
Date: Thu, 24 Jan 2013 10:11:08 +0800 [thread overview]
Message-ID: <20130124021108.GB32496@kernel.org> (raw)
In-Reply-To: <e59b7d62-67f5-4afb-8c8e-d422d3e82832@default>
On Wed, Jan 23, 2013 at 03:05:22PM -0800, Dan Magenheimer wrote:
> I would be very interested in this topic.
>
> > Because of high density, low power and low price, flash storage (SSD) is a good
> > candidate to partially replace DRAM. A quick answer for this is using SSD as
> > swap. But Linux swap is designed for slow hard disk storage. There are a lot of
> > challenges to efficiently use SSD for swap:
> >
> > 1. Lock contentions (swap_lock, anon_vma mutex, swap address space lock)
> > 2. TLB flush overhead. To reclaim one page, we need at least 2 TLB flush. This
> > overhead is very high even in a normal 2-socket machine.
> > 3. Better swap IO pattern. Both direct and kswapd page reclaim can do swap,
> > which makes swap IO pattern is interleave. Block layer isn't always efficient
> > to do request merge. Such IO pattern also makes swap prefetch hard.
>
> Shaohua --
>
> Have you considered the possibility of subverting the block layer entirely
> and accessing the SSD like slow RAM rather than a fast I/O device? E.g.
> something like NVME and as in this paper?
>
> http://static.usenix.org/events/fast12/tech/full_papers/Yang.pdf
>
> If you think this could be an option, it could make a very
> interesting backend to frontswap (something like ramster).
We had discussion about this before, but looks this requires very low latency
storage, didn't take it serious yet.
Thanks,
Shaohua
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-01-24 2:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <766b9855-adf5-47ce-9484-971f88ff0e54@default>
2013-01-23 23:05 ` [LSF/MM TOPIC]swap improvements for fast SSD Dan Magenheimer
2013-01-24 2:11 ` Shaohua Li [this message]
2013-01-22 6:53 Shaohua Li
2013-01-23 7:58 ` Minchan Kim
2013-01-23 19:04 ` Seth Jennings
2013-01-24 1:40 ` Minchan Kim
2013-01-24 8:29 ` Simon Jeons
2013-01-24 2:02 ` Shaohua Li
2013-01-24 7:52 ` Simon Jeons
2013-01-24 9:09 ` Simon Jeons
2013-01-26 4:40 ` Kyungmin Park
2013-01-27 0:26 ` Simon Jeons
2013-01-27 14:18 ` Shaohua Li
2013-01-28 7:37 ` Kyungmin Park
2013-02-01 12:37 ` Kyungmin Park
2013-02-04 4:56 ` Hugh Dickins
2013-02-19 6:15 ` Shaohua Li
2013-02-19 19:41 ` Hugh Dickins
2013-04-05 0:17 ` Simon Jeons
2013-04-05 8:08 ` Minchan Kim
2013-01-23 16:56 ` Seth Jennings
2013-01-24 6:28 ` Simon Jeons
2013-03-15 9:39 ` Simon Jeons
2013-03-18 10:38 ` Bob Liu
2013-03-19 1:27 ` Shaohua Li
2013-03-19 1:32 ` Simon Jeons
2013-03-19 5:57 ` Shaohua Li
2013-03-19 6:10 ` Simon Jeons
2013-03-19 4:25 ` Wanpeng Li
2013-03-19 4:25 ` Wanpeng Li
2013-04-28 8:12 ` Simon Jeons
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=20130124021108.GB32496@kernel.org \
--to=shli@kernel.org \
--cc=dan.magenheimer@oracle.com \
--cc=linux-mm@kvack.org \
--cc=shli@fusionio.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.