From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@zip.com.au>
Cc: Dave Jones <davej@codemonkey.org.uk>,
"Randy.Dunlap" <rddunlap@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [announce] swap mini-howto
Date: Sat, 2 Nov 2002 17:55:03 +0100 [thread overview]
Message-ID: <20021102165503.GC1983@elf.ucw.cz> (raw)
In-Reply-To: <3DC3207A.450402B3@zip.com.au>
Hi!
> That has changed in 2.5. Swapping onto a regular file has no
> disadvantage wrt swapping onto a block device. The kernel does
> not need to allocate any memory at all to get a swapcache page
> onto disk.
>
> Which is interesting. Because swapfiles are much easier to administer,
> and much easier to stripe. Adding, removing and resizing is simplified.
> Distributors of 2.6-based kernels could consider doing away with
> swapdevs altogether.
Well, you can swsusp to partition. You can't swsusp to a file, as that
is very hard to do.
Pavel
--
When do you have heart between your knees?
next prev parent reply other threads:[~2002-11-02 17:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 23:58 [announce] swap mini-howto Randy.Dunlap
2002-11-02 0:09 ` Dave Jones
2002-11-02 0:07 ` Randy.Dunlap
2002-11-02 0:46 ` Andrew Morton
2002-11-02 8:26 ` Jeff Garzik
2002-11-02 10:02 ` Andrew Morton
2002-11-02 23:31 ` Jeff Garzik
2002-11-02 11:22 ` Troels Walsted Hansen
2002-11-04 10:47 ` Richard Russon
2002-11-02 16:55 ` Pavel Machek [this message]
2002-11-02 21:23 ` Rik van Riel
2002-11-02 21:28 ` Pavel Machek
2002-11-02 0:19 ` Andries Brouwer
2002-11-02 0:25 ` Randy.Dunlap
2002-11-02 11:19 ` Andries Brouwer
2002-11-05 5:54 ` [announce] swap mini-howto (updated) Randy.Dunlap
2002-11-02 1:01 ` [announce] swap mini-howto Nicolas Pitre
2002-11-02 1:23 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2002-11-03 10:56 Gabor MICSKO
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=20021102165503.GC1983@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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