All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Pisarcik <boris@acheron.sk>
To: linux-kernel@vger.kernel.org
Subject: Re: Is swap == 2 * RAM a permanent thing?
Date: Sat, 17 Mar 2001 18:59:15 +0100	[thread overview]
Message-ID: <20010317185915.A5154@Boris> (raw)
In-Reply-To: <Pine.LNX.4.21.0103151421380.22425-100000@benatar.snurgle.org> <Pine.LNX.4.33.0103152344260.1320-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33.0103152344260.1320-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Thu, Mar 15, 2001 at 11:44:52PM -0300

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

On Thu, Mar 15, 2001 at 11:44:52PM -0300, Rik van Riel wrote:
> On Thu, 15 Mar 2001, William T Wilson wrote:
> 
> > it seems to me that in 2.2.x it looks like this:
> >
> > total usage == swap + RAM
> > under 2.4.x it looks like:
> > total usage == swap
> 
>   total usage == maximum(swap, ram)

Hi, 

Do you in fact talk about 
  1) curren usage == maximum(swap, ram)
     or
  2) virtual ram capacity == maximum(swap, ram)
?

I'm a bit confused.

My next question is: some time ago i've read, that code segments of process,
which comes from executable and should stay unmodified during process
duration, are not swapped into swap space, cause they can be restored
back from the executable. This should be ok, because in protect mode
no one can write into code seg. This does seem to be true for win, because
i cannot delete executable file when it's just run, but under linux
i can delete /bin/bash without any problem. 

Why this is so ?

Because of security ? Say my disk gets corrupted right at blocks executable
image si contained and swapping in page(s) from this errorneous area
should lock/corrupt system ?

Code content can be changed indirectly in case data or some read-write segment overlaps 
code segment. Does linux count with such a situation ? (may data segment
overlap code seg ?)



Thanks                                                                Boro


email: boris@acheron.sk 

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

  parent reply	other threads:[~2001-03-17 17:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 17:19 Is swap == 2 * RAM a permanent thing? Torrey Hoffman
2001-03-15 19:22 ` William T Wilson
2001-03-16  2:44   ` Rik van Riel
2001-03-15 20:11     ` LA Walsh
2001-03-16  3:56       ` Rik van Riel
2001-03-15 21:45     ` Andrzej Krzysztofowicz
2001-03-16  5:08       ` Rik van Riel
2001-03-19 15:21         ` Guennadi Liakhovetski
2001-03-17 17:59     ` Boris Pisarcik [this message]
2001-03-17 17:53       ` Alexander Viro
  -- strict thread matches above, loose matches on Subject: below --
2001-03-15 12:28 Mike A. Harris
2001-03-15 13:08 ` Rik van Riel
2001-03-15 14:24   ` Mike Harrold
2001-03-16  0:47     ` Rik van Riel
2001-03-15 16:09   ` christophe barbe
2001-03-15 23:26     ` Rik van Riel
2001-03-15 17:20       ` christophe barbe
2001-03-15 17:43       ` James Lewis Nance
2001-03-16  1:25         ` Rik van Riel
2001-03-15 15:23 ` Ketil Froyn

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=20010317185915.A5154@Boris \
    --to=boris@acheron.sk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.