From: Eric Sandall <eric@sandall.us>
To: Wakko Warner <wakko@animx.eu.org>
Cc: Jeremy Nickurak <atrus@lkml.spam.rifetech.com>,
linux-kernel@vger.kernel.org
Subject: Re: Swap partition vs swap file
Date: Sat, 9 Jul 2005 15:59:39 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0507091559030.486@cerberus> (raw)
In-Reply-To: <20050708224106.GA10649@animx.eu.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 8 Jul 2005, Wakko Warner wrote:
> Jeremy Nickurak wrote:
>> 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.
>
> Of course, now this begs the question: Is it possible to create a large file
> w/o actually writing that much to the device (ie uninitialized). There's
> absolutely no reason that a swap file needs to be fully initialized, only
> part which mkswap does. Of course, I would expect that ONLY root beable to
> do this. (or capsysadmin or whatever the caps are)
That would make the swap file fragment as it's used, instead of
allocating one big file (the entire file) at once (and hopefully get
one contiguous chunk of the disk).
- -sandalle
- --
Eric Sandall | Source Mage GNU/Linux Developer
eric@sandall.us | http://www.sourcemage.org/
http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/ #196285 | http://www.shock.wsu.edu/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC0FbfHXt9dKjv3WERApKjAJ9ZObnrYWCmTyZW0ChggtgGjTKIvQCfbnvm
/U4zfjTYqMxEd5vmIRe1wbM=
=smCj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-07-09 22:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 0:57 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
2005-07-08 21:35 ` Helge Hafting
2005-07-08 22:41 ` Wakko Warner
2005-07-09 22:59 ` Eric Sandall [this message]
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=Pine.LNX.4.63.0507091559030.486@cerberus \
--to=eric@sandall.us \
--cc=atrus@lkml.spam.rifetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wakko@animx.eu.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
all inboxes | Powered by JetHome®