[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <r2h63b77a231004230935hae38da68l2de84cb1a2084a6b@mail.gmail.com>
Date: Fri, 23 Apr 2010 09:35:14 -0700
From: Jiahua <jiahua@...il.com>
To: Dan Magenheimer <dan.magenheimer@...cle.com>
Cc: Avi Kivity <avi@...hat.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, jeremy@...p.org, hugh.dickins@...cali.co.uk,
ngupta@...are.org, JBeulich@...ell.com, chris.mason@...cle.com,
kurt.hackel@...cle.com, dave.mccracken@...cle.com, npiggin@...e.de,
akpm@...ux-foundation.org, riel@...hat.com
Subject: Re: Frontswap [PATCH 0/4] (was Transcendent Memory): overview
On Fri, Apr 23, 2010 at 6:47 AM, Dan Magenheimer
<dan.magenheimer@...cle.com> wrote:
> If I understand correctly, SSDs work much more efficiently when
> writing 64KB blocks. So much more efficiently in fact that waiting
> to collect 16 4KB pages (by first copying them to fill a 64KB buffer)
> will be faster than page-at-a-time DMA'ing them. If so, the
> frontswap interface, backed by an asynchronous "buffering layer"
> which collects 16 pages before writing to the SSD, may work
> very nicely. Again this is still just speculation... I was
> only pointing out that zero-copy DMA may not always be the best
> solution.
I guess you are talking about the write amplification issue of SSD. In
fact, most of the new generation drives already solved the problem
with log like structure. Even with the old drives, the size of the
writes depends on the the size of the erase block, which is not
necessary 64KB.
Jiahua
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists