From: Arnd Bergmann <arnd@arndb.de>
To: Hugh Dickins <hughd@google.com>
Cc: linaro-kernel@lists.linaro.org, Rik van Riel <riel@redhat.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Alex Lemberg <alex.lemberg@sandisk.com>,
linux-kernel@vger.kernel.org,
"Luca Porzio (lporzio)" <lporzio@micron.com>,
linux-mm@kvack.org, Hyojin Jeong <syr.jeong@samsung.com>,
kernel-team@android.com, Yejin Moon <yejin.moon@samsung.com>
Subject: Re: swap on eMMC and other flash
Date: Mon, 2 Apr 2012 14:55:24 +0000 [thread overview]
Message-ID: <201204021455.25029.arnd@arndb.de> (raw)
In-Reply-To: <alpine.LSU.2.00.1204020734560.1847@eggly.anvils>
On Monday 02 April 2012, Hugh Dickins wrote:
> On Mon, 2 Apr 2012, Arnd Bergmann wrote:
> >
> > Another option would be batched discard as we do it for file systems:
> > occasionally stop writing to swap space and scanning for areas that
> > have become available since the last discard, then send discard
> > commands for those.
>
> I'm not sure whether you've missed "swapon --discard", which switches
> on discard_swap_cluster() just before we allocate from a new cluster;
> or whether you're musing that it's no use to you because you want to
> repurpose the swap cluster to match erase block: I'm mentioning it in
> case you missed that it's already there (but few use it, since even
> done at that scale it's often more trouble than it's worth).
I actually argued that discard_swap_cluster is exactly the right thing
to do, especially when clusters match erase blocks on the less capable
devices like SD cards.
Luca was arguing that on some hardware there is no point in ever
submitting a discard just before we start reusing space, because
at that point it the hardware already discards the old data by
overwriting the logical addresses with new blocks, while
issuing a discard on all blocks as soon as they become available
would make a bigger difference. I would be interested in hearing
from Hyojin Jeong and Alex Lemberg what they think is the best
time to issue a discard, because they would know about other hardware
than Luca.
Arnd
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-04-02 14:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 17:44 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 [this message]
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
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
2012-04-06 7:15 ` Minchan Kim
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=201204021455.25029.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alex.lemberg@sandisk.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=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