From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Samuel <chris@csamuel.org>
Subject: btrfs and swap files on SSD's ?
Date: Sat, 17 Jan 2009 11:10:22 +1100
Message-ID: <200901171110.22803.chris@csamuel.org>
Mime-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart4542476.TjQD5k0IWE";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
To: "linux-btrfs" <linux-btrfs@vger.kernel.org>
Return-path: <linux-btrfs-owner@vger.kernel.org>
List-ID: <linux-btrfs.vger.kernel.org>

--nextPart4542476.TjQD5k0IWE
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi folks,

Someone on the OpenMoko community list commented recently about having crea=
ted=20
a swap file on the SD card of their OpenMoko Neo phone and said that they'd=
=20
been lazy as they'd not made a swap partition.

My thought was that with an SSD aware filesystem like btrfs a swapfile woul=
d=20
actually be a smarter move than a swap partition because it lets the=20
filesystem try and even the wear generated by access to it which a swap=20
partition will not have the freedom to do.

To me that makes logical sense but given the complexity of the kernel and=20
btrfs is it a fair comment to make and, also, would that be the case with=20
btrfs at present ?

cheers!
Chris
=2D-=20
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

This email may come with a PGP signature as a file. Do not panic.
=46or more info see: http://en.wikipedia.org/wiki/OpenPGP


--nextPart4542476.TjQD5k0IWE
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUASXEh7o1yjaOTJg85AQIIIwgAj9S769RqZgmVDnpcaQL7/4I4hc1myl+d
0DnAd4gFSLK5YD4ezIViTqr2W7nEIQcBhp554147G4rczCnjAmf4h5ykihZK8W3Z
+sYWLCS7BOxGNEdfxC6iLF5ojo0a5RfsGMwl9vHGNwS7HO1V9UNmrzwUJJsKd0oh
YwUDqQvTnMe0d0LPF/q8ytOxB3IMVc+/txh9LEzGdN3ez1+P8U/RGi2bHy0TEmq3
+/VQZs/A/U+oCjXEbfrhY9KGIMsJwPCcNEmZkb4FtbFRHE4YRnSuWA06FksNCM0u
vBR1tCU9pxnX1tK9qUNghY1hEvEReC5mgJyKqRKO0HhatZogrzdM+A==
=gJSD
-----END PGP SIGNATURE-----

--nextPart4542476.TjQD5k0IWE--