linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Lang <david.lang@digitalinsight.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: John Ripley <jripley@riohome.com>,
	linux-kernel@vger.kernel.org,
	VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
Subject: Re: COW fs (Re: Editing-in-place of a large file)
Date: Sun, 9 Sep 2001 19:58:27 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0109091957120.31268-100000@dlang.diginsite.com> (raw)
In-Reply-To: <20010910023641Z16066-26183+701@humbolt.nl.linux.org>

if sectors full of zeros are really that common then they should never be
swapped out, just a new page allocated and zeroed when it would be swapped
back in. Even better then combining all of them into one block on disk.

David Lang

 On Mon, 10 Sep 2001, Daniel Phillips wrote:

> Date: Mon, 10 Sep 2001 04:43:53 +0200
> From: Daniel Phillips <phillips@bonn-fries.net>
> To: John Ripley <jripley@riohome.com>, linux-kernel@vger.kernel.org
> Cc: VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
> Subject: Re: COW fs (Re: Editing-in-place of a large file)
>
> On September 9, 2001 06:30 pm, John Ripley wrote:
> > Interesting results for the swap partitions. Probably full of zeros.
>
> It doesn't make a lot of sense to spend 30-35% of your swap bandwidth
> swapping zeros in and out, does it?
>
> --
> Daniel
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2001-09-10  2:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-02 20:21 Editing-in-place of a large file Bob McElrath
2001-09-02 21:28 ` COW fs (Re: Editing-in-place of a large file) VDA
2001-09-09 14:46   ` John Ripley
2001-09-09 16:30     ` John Ripley
2001-09-10  2:43       ` Daniel Phillips
2001-09-10  2:58         ` David Lang [this message]
2001-09-09 17:41     ` Xavier Bestel
2001-09-10  1:29       ` John Ripley
2001-09-10  6:45         ` Ragnar Kjørstad
2001-09-14 10:06         ` Pavel Machek
2001-09-10 11:11       ` Ihar Filipau
2001-09-10 16:10         ` Kari Hurtta
2001-09-14 10:03     ` Pavel Machek
2001-09-10  9:28   ` VDA
2001-09-10  9:35     ` John P. Looney
2001-09-02 21:30 ` Editing-in-place of a large file Ingo Oeser
2001-09-03  0:59   ` Larry McVoy
2001-09-03  1:24     ` Ingo Oeser
2001-09-03  1:31       ` Alan Cox
2001-09-03  1:50         ` Ingo Oeser
2001-09-03 10:48           ` Alan Cox
2001-09-03 14:31             ` Daniel Phillips
2001-09-03 14:46             ` Bob McElrath
2001-09-03 14:54               ` Alan Cox
2001-09-03 15:42                 ` Doug McNaught
2001-09-03 15:11               ` Richard Guenther
2001-09-03 21:19             ` Ben Ford
2001-09-03  4:27       ` Bob McElrath
2001-09-03  1:30     ` Daniel Phillips

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.33.0109091957120.31268-100000@dlang.diginsite.com \
    --to=david.lang@digitalinsight.com \
    --cc=VDA@port.imtp.ilyichevsk.odessa.ua \
    --cc=jripley@riohome.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    /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;
as well as URLs for NNTP newsgroup(s).