public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Nickurak <atrus@lkml.spam.rifetech.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Swap partition vs swap file
Date: Fri, 08 Jul 2005 09:35:58 -0600	[thread overview]
Message-ID: <1120836958.16935.1.camel@localhost> (raw)
In-Reply-To: <E1DqhZV-0004yW-00@calista.eckenfels.6bone.ka-ip.net>

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

On ven, 2005-07-08 at 03:22 +0200, Bernd Eckenfels wrote:
> No, it is creating files by appending just like any other file write. One
> could think about a call to create unfragmented files however since this is
> not always working best is to create those files young or defragment them
> before usage.

Except that this defeats one of the biggest advantages a swap file has
over a swap partition: the ability to easilly reconfigure the amount of
hd space reserved for swap.

-- 
Jeremy Nickurak <atrus@lkml.spam.rifetech.com>

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

  reply	other threads:[~2005-07-08 15:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29  0:57 Swap partition vs swap file Mike Richards
2005-06-29  5:03 ` Andrew Morton
2005-06-29 10:37   ` Marat Buharov
2005-06-29 11:46     ` Douglas McNaught
2005-07-07 19:50   ` Mike Richards
2005-07-07 21:59     ` Andrew Morton
2005-07-08  0:44       ` Coywolf Qi Hunt
2005-07-08  1:22         ` Bernd Eckenfels
2005-07-08 15:35           ` Jeremy Nickurak [this message]
2005-07-08 21:35             ` Helge Hafting
2005-07-08 22:41             ` Wakko Warner
2005-07-09 22:59               ` Eric Sandall
2005-07-10  1:45                 ` Wakko Warner
2005-07-10  2:14                   ` Bernd Eckenfels
2005-07-10 12:54                     ` Wakko Warner
2005-07-10 21:40                       ` Bernd Eckenfels
2005-07-11 11:10                       ` Helge Hafting
2005-07-12 21:53                         ` Wakko Warner
2005-07-13 10:58                           ` Jan Engelhardt

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=1120836958.16935.1.camel@localhost \
    --to=atrus@lkml.spam.rifetech.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox