From: Arnd Bergmann <arnd@arndb.de>
To: 정효진 <syr.jeong@samsung.com>
Cc: "'Minchan Kim'" <minchan@kernel.org>,
"'Alex Lemberg'" <Alex.Lemberg@sandisk.com>,
linaro-kernel@lists.linaro.org,
"'Rik van Riel'" <riel@redhat.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
"'Luca Porzio (lporzio)'" <lporzio@micron.com>,
linux-mm@kvack.org, kernel-team@android.com,
"'Yejin Moon'" <yejin.moon@samsung.com>,
"'Hugh Dickins'" <hughd@google.com>,
"'Yaniv Iarovici'" <Yaniv.Iarovici@sandisk.com>,
cpgs@samsung.com
Subject: Re: swap on eMMC and other flash
Date: Mon, 9 Apr 2012 12:54:39 +0000 [thread overview]
Message-ID: <201204091254.39380.arnd@arndb.de> (raw)
In-Reply-To: <006f01cd1623$ac4a2860$04de7920$%jeong@samsung.com>
On Monday 09 April 2012, 정효진 wrote:
> If swap system use 512KB page and issue Discard/Trim align with 512KB, eMMC make best
> performance as of today. However, large page size in swap partition may not best way
> in Linux system level.
> I'm not sure that the best page size between Swap system and eMMC device.
Can you explain the significance of the 512KB size? I've seen devices report 512KB
erase size, although measurements clearly showed an erase block size of 8MB and I
do not understand this discprepancy.
Right now, we always send discards of 1MB clusters to the device, which does what
you want, although I'm not sure if those clusters are naturally aligned to the start
of the partition. Obviously this also requires aligning the start of the partition
to the erase block size, but most devices should already get that right nowadays.
Arnd
next prev parent reply other threads:[~2012-04-09 12:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 17:44 swap on eMMC and other flash Arnd Bergmann
2012-03-30 18:50 ` Arnd Bergmann
2012-03-30 22:08 ` Zach Pfeffer
2012-03-31 9:24 ` Arnd Bergmann
2012-04-03 18:17 ` Zach Pfeffer
2012-03-31 20:29 ` Hugh Dickins
2012-04-02 11:45 ` Arnd Bergmann
2012-04-02 14:41 ` Hugh Dickins
2012-04-02 14:55 ` Arnd Bergmann
2012-04-05 0:17 ` 정효진
2012-04-09 12:50 ` Arnd Bergmann
2012-04-08 13:50 ` Alex Lemberg
2012-04-09 2:14 ` Minchan Kim
2012-04-09 7:37 ` 정효진
2012-04-09 8:11 ` Minchan Kim
2012-04-09 13:00 ` Arnd Bergmann
2012-04-10 1:10 ` Minchan Kim
2012-04-10 8:40 ` Arnd Bergmann
2012-04-12 8:32 ` Luca Porzio (lporzio)
2012-04-09 12:54 ` Arnd Bergmann [this message]
2012-04-02 12:52 ` Luca Porzio (lporzio)
2012-04-02 14:58 ` Hugh Dickins
2012-04-02 16:51 ` Rik van Riel
2012-04-04 12:21 ` Adrian Hunter
2012-04-04 12:47 ` Arnd Bergmann
2012-04-11 10:28 ` Adrian Hunter
2012-07-16 13:29 ` Pavel Machek
[not found] ` <CAEwNFnA2GeOayw2sJ_KXv4qOdC50_Nt2KoK796YmQF+YV1GiEA@mail.gmail.com>
2012-04-06 16:16 ` Arnd Bergmann
2012-04-09 2:06 ` Minchan Kim
2012-04-09 12:35 ` Arnd Bergmann
2012-04-10 0:57 ` Minchan Kim
2012-04-10 8:32 ` Arnd Bergmann
2012-04-11 9:54 ` Minchan Kim
2012-04-11 15:57 ` Arnd Bergmann
2012-04-12 2:36 ` Minchan Kim
2012-04-16 18:22 ` Stephan Uphoff
2012-04-16 18:59 ` Arnd Bergmann
2012-04-16 21:12 ` Stephan Uphoff
2012-04-17 2:18 ` Minchan Kim
2012-04-17 2:05 ` Minchan Kim
2012-04-27 7:34 ` Luca Porzio (lporzio)
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=201204091254.39380.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Alex.Lemberg@sandisk.com \
--cc=Yaniv.Iarovici@sandisk.com \
--cc=cpgs@samsung.com \
--cc=hughd@google.com \
--cc=kernel-team@android.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lporzio@micron.com \
--cc=minchan@kernel.org \
--cc=riel@redhat.com \
--cc=syr.jeong@samsung.com \
--cc=yejin.moon@samsung.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).