public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paweł Zadrąg" <p.zeddi@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: How to tune kernel to swap more often (video ram swap)
Date: Sun, 5 Feb 2006 11:04:25 +0100	[thread overview]
Message-ID: <b92f4fd10602050204g41f70f70p@mail.gmail.com> (raw)

Yo...

In normal case, using harddisk as a swap space i should ask how to cut
down swapping, or make swapping when idle, etc... My case is a little
bit diffrent... I have a 256MB video card, while 240MB of it is used
as a swap space. And the question is: how to tune kernel to swap more
often. I known swapped memory must be copied back to ram before beeing
used, so i'm looking for a reasonable tunning values...

What do You think about that mighty list ?

--
Chears,
zeddi

             reply	other threads:[~2006-02-05 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-05 10:04 Paweł Zadrąg [this message]
2006-02-05 11:04 ` How to tune kernel to swap more often (video ram swap) Marc Koschewski
2006-02-05 11:10 ` [OT] " Eric Piel
2006-02-05 11:17   ` Tomasz Torcz
2006-02-06  7:52     ` Helge Hafting

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=b92f4fd10602050204g41f70f70p@mail.gmail.com \
    --to=p.zeddi@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