All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Samuel <chris@csamuel.org>
To: "linux-btrfs" <linux-btrfs@vger.kernel.org>
Subject: btrfs and swap files on SSD's ?
Date: Sat, 17 Jan 2009 11:10:22 +1100	[thread overview]
Message-ID: <200901171110.22803.chris@csamuel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 877 bytes --]

Hi folks,

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

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

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

cheers!
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

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


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

             reply	other threads:[~2009-01-17  0:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17  0:10 Chris Samuel [this message]
2009-01-19 16:22 ` btrfs and swap files on SSD's ? Chris Mason
2009-01-20 10:41   ` Kaspar Schleiser
2009-01-20 13:02     ` Chris Mason
2009-01-20 13:51       ` Dmitri Nikulin
2009-01-20 14:31         ` Chris Mason
2009-01-20 16:35           ` Anthony Roberts
2009-01-20 16:41             ` Chris Mason
2009-01-21  6:15         ` Andi Kleen

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=200901171110.22803.chris@csamuel.org \
    --to=chris@csamuel.org \
    --cc=linux-btrfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.