mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Egger <degger@fhm.edu>
To: Jan Hudec <bulb@cimice.maxinet.cz>
Cc: Jean-Eric Cuendet <Jean-Eric.Cuendet@linkvest.com>,
	linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: Pages swapped out even when free memory available...
Date: 20 Aug 2002 16:11:01 +0200	[thread overview]
Message-ID: <1029852661.547.4.camel@sonja.de.interearth.com> (raw)
In-Reply-To: <20020820102816.GC6981@vagabond>

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

Am Die, 2002-08-20 um 12.28 schrieb Jan Hudec:

> Don't do it. In user-land, you simply don't have the info kernel does.
> Gimp tries to do things like this and results are truly horrible.
> It forces machine in deep swap if you set the cache large, while with
> small cache the actual size does not matter much as kernel takes care of
> the real caching.
 
> You should rather open a file you want to swap in, mmap it and only keep
> minimum data in other memory. Only reason to do even this may be, that
> the data may get too large to fit in swap. For all other reasons you
> should just let kernel do it's work.

Interesting you mention it. A week ago I started a thread exactly for
that reason; I implemented GIMPs tilemanagement using mmap but
unfortunately the performance sucks even more than GIMPs "clever" 
swapping. That having said it has at least one more severe disadvantage:
The maximum amount of mmapable memory is far less than the maximum
filesize with large file support.

-- 
Servus,
       Daniel

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2002-08-20 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <61FEFD6522F0F142B36E3F6CE511A4F01D37CC@hermes.linkvest.com>
2002-08-20 10:28 ` Jan Hudec
2002-08-20 14:11   ` Daniel Egger [this message]

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=1029852661.547.4.camel@sonja.de.interearth.com \
    --to=degger@fhm.edu \
    --cc=Jean-Eric.Cuendet@linkvest.com \
    --cc=bulb@cimice.maxinet.cz \
    --cc=kernelnewbies@nl.linux.org \
    --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

all inboxes | Powered by JetHome®