From: Minchan Kim <minchan@kernel.org>
To: Simon Jeons <simon.jeons@gmail.com>
Cc: Shaohua Li <shli@kernel.org>,
lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
Rik van Riel <riel@redhat.com>
Subject: Re: [LSF/MM TOPIC]swap improvements for fast SSD
Date: Fri, 5 Apr 2013 17:08:17 +0900 [thread overview]
Message-ID: <20130405080817.GC32126@blaptop> (raw)
In-Reply-To: <515E17FC.9050008@gmail.com>
On Fri, Apr 05, 2013 at 08:17:00AM +0800, Simon Jeons wrote:
> Hi Minchan,
> On 01/23/2013 03:58 PM, Minchan Kim wrote:
> >On Tue, Jan 22, 2013 at 02:53:41PM +0800, Shaohua Li wrote:
> >>Hi,
> >>
> >>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:
> >Many of below item could be applied in in-memory swap like zram, zcache.
> >
> >>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.
> >Agreed.
> >
> >>4. Swap map scan overhead. Swap in-memory map scan scans an array, which is
> >>very inefficient, especially if swap storage is fast.
> >Agreed.
> >
> >>5. SSD related optimization, mainly discard support
> >>6. Better swap prefetch algorithm. Besides item 3, sequentially accessed pages
> >>aren't always in LRU list adjacently, so page reclaim will not swap such pages
> >>in adjacent storage sectors. This makes swap prefetch hard.
> >One of problem is LRU churning and I wanted to try to fix it.
> >http://marc.info/?l=linux-mm&m=130978831028952&w=4
>
> I'm interested in this feature, why it didn't merged? what's the
> fatal issue in your patchset?
> http://lwn.net/Articles/449866/
There wasn't any fatal issue, AFAIRC but some people had a concern about
balancing between code complexity and benefit and dragged for a long time
and I lost interest.
> You mentioned test script and all-at-once patch, but I can't get
> them from the URL, could you tell me how to get it?
You can google it and google will find it in a few second.
http://www.filewatcher.com/b/ftp/ftp.cs.huji.ac.il/mirror/linux/kernel/linux/kernel/people/minchan/inorder_putback/v4-0.html
--
Kind regards,
Minchan Kim
--
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-04-05 8:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 6:53 [LSF/MM TOPIC]swap improvements for fast SSD 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 [this message]
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
[not found] <766b9855-adf5-47ce-9484-971f88ff0e54@default>
2013-01-23 23:05 ` Dan Magenheimer
2013-01-24 2:11 ` Shaohua Li
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=20130405080817.GC32126@blaptop \
--to=minchan@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=riel@redhat.com \
--cc=shli@kernel.org \
--cc=simon.jeons@gmail.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;
as well as URLs for NNTP newsgroup(s).