- To: Arnd Bergmann <arnd@xxxxxxxx>, Minchan Kim <minchan@xxxxxxxxxx>
- Subject: RE: swap on eMMC and other flash
- From: "Luca Porzio (lporzio)" <lporzio@xxxxxxxxxx>
- Date: Thu, 12 Apr 2012 08:32:57 +0000
- Accept-language: it-IT, en-US
- Cc: 정효진 <syr.jeong@xxxxxxxxxxx>, "'Alex Lemberg'" <Alex.Lemberg@xxxxxxxxxxx>, "linaro-kernel@xxxxxxxxxxxxxxxx" <linaro-kernel@xxxxxxxxxxxxxxxx>, "'Rik van Riel'" <riel@xxxxxxxxxx>, "linux-mmc@xxxxxxxxxxxxxxx" <linux-mmc@xxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, "kernel-team@xxxxxxxxxxx" <kernel-team@xxxxxxxxxxx>, "'Yejin Moon'" <yejin.moon@xxxxxxxxxxx>, "'Hugh Dickins'" <hughd@xxxxxxxxxx>, "'Yaniv Iarovici'" <Yaniv.Iarovici@xxxxxxxxxxx>, "cpgs@xxxxxxxxxxx" <cpgs@xxxxxxxxxxx>
- Delivered-to: linux-mm-outgoing@xxxxxxxxx
- Delivered-to: int-list-linux-mm@xxxxxxxxx
- Delivered-to: linux-mm@xxxxxxxxx
- In-reply-to: <201204100840.11763.arnd@arndb.de>
- Thread-index: AQHNDpzybzWjK4z/iEWbFOApOu/42JaDDSoAgAGt6QCAApJvAIAAMT0AgAADxACACVvKAIAAz84AgABafICAAAlnAIAAUMEAgADL1gCAAH2/gIABVeiA
- Thread-topic: swap on eMMC and other flash
Hi All,
> -----Original Message-----
> From: linux-mmc-owner@xxxxxxxxxxxxxxx [mailto:linux-mmc-owner@xxxxxxxxxxxxxxx]
> On Behalf Of Arnd Bergmann
> Sent: Tuesday, April 10, 2012 1:40 AM
> To: Minchan Kim
> Cc: 정효진; 'Alex Lemberg'; linaro-kernel@xxxxxxxxxxxxxxxx; 'Rik van Riel';
> linux-mmc@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; Luca Porzio
> (lporzio); linux-mm@xxxxxxxxx; kernel-team@xxxxxxxxxxx; 'Yejin Moon'; 'Hugh
> Dickins'; 'Yaniv Iarovici'; cpgs@xxxxxxxxxxx
> Subject: Re: swap on eMMC and other flash
>
> On Tuesday 10 April 2012, Minchan Kim wrote:
> > I think it's not good approach.
> > How long does it take to know such parameters?
> > I guess it's not short so that mkfs/mkswap would be very long
> > dramatically. If needed, let's maintain it as another tool.
>
> I haven't come up with a way that is both fast and reliable.
> A very fast method is to time short read requests across potential
> erase block boundaries and see which ones are faster than others,
> this works on about 3 out of 4 devices.
>
> For the other devices, I currently use a fairly manual process that
> times a lot of write requests and can take a long time.
>
> > If storage vendors break such fields, it doesn't work well on linux
> > which is very popular on mobile world today and user will not use such
> > vendor devices and company will be gone. Let's give such pressure to
> > them and make vendor keep in promise.
>
> This could work for eMMC, yes.
>
I like it ;)
> The SD card standard makes it impossible to write the correct value for
> most devices, it only supports power-of-two values up to 4MB for SDHC,
> and larger values (I believe 8, 12, 16, 24, ... 64) for SDXC, but a lot
> of SDHC cards nowadays use 1.5, 3, 6 or 8 MB erase blocks.
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
��.n������g����a����&ޖ)���)��h���&������梷�����Ǟ�m������)�����b�n���y��{^�w�r���&�i��('����춊m�鞵��â����چ�����i�������$����
[Site Home]
[Linux ARM Kernel]
[Linux ARM]
[Linux Omap]
[Fedora ARM]
[IETF Annouce]
[Security]
[Bugtraq]
[Linux]
[Linux OMAP]
[Linux MIPS]
[ECOS]
[Tools]
[DDR & Rambus]
[Asterisk Internet PBX]
[Linux API]
[Monitors]