public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marat Buharov <marat.buharov@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Swap partition vs swap file
Date: Wed, 29 Jun 2005 14:37:56 +0400	[thread overview]
Message-ID: <698310e10506290337681fad81@mail.gmail.com> (raw)
In-Reply-To: <20050628220334.66da4656.akpm@osdl.org>

Hmm, but what about tells mkswap(8) tells:
"...Note that a swap file must not contain any holes (so, using  cp
(1) to create the file is not acceptable)..."?

If swap file will be fragmented it will contain holes.
Or what type of holes can cp(1) can create, which are not usefull for mkswap(8)?

2005/6/29, Andrew Morton <akpm@osdl.org>:
> Mike Richards <mrmikerich@gmail.com> wrote:
> >
> > Given this situation, is there any significant performance or
> >  stability advantage to using a swap partition instead of a swap file?
> 
> In 2.6 they have the same reliability and they will have the same
> performance unless the swapfile is badly fragmented.
>

  reply	other threads:[~2005-06-29 10:38 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 [this message]
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
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=698310e10506290337681fad81@mail.gmail.com \
    --to=marat.buharov@gmail.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