mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: linux-kernel@vger.kernel.org
Subject: Re:swap prefetching merge plans
Date: Thu, 23 Mar 2006 08:56:24 +0100	[thread overview]
Message-ID: <200603230856.24091.volker.armin.hemmann@tu-clausthal.de> (raw)

Hi,

I am just a user, but I would love to see this feature.

After compiling stuff, I have usually some kb in swap (300kb, 360 kb), and 
lots of free ram. But even this few kb make my KDE desktop extremly sluggish. 
It feels, like every byte is fetched individually and always the wrong stuff 
ends in swap.

The only 'workaround' so far is to do a 'swapoff -a&& swapon -a' which not 
only clears swap, but make my box blazzingly fast again (thank you guys, 
besides this little swap annoyance you all do a great job). 

So everything that makes the situation better (swap in of data faster) is 
highly welcome. The CPU is bored most of the time anyway and as I wrote 
above, usually lots of ram are free. So why not use the free ram and free CPU 
cycles?

The compelling argument is: swap is extremly slow. It is so slow that you can 
go out, plant a tree, build a house and father a son while I am waiting for 
some few kb to get fetched from it. Everything that reduces swap access when 
the data is needed, is IMHO a good thing. Oh, and the harddisk is not slow. 
Only swap is.

Glück Auf,
Volker

             reply	other threads:[~2006-03-23  7:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23  7:56 Hemmann, Volker Armin [this message]
2006-03-23  8:26 ` swap " Nick Piggin
2006-03-23 11:47   ` Jan Knutar
2006-03-23 13:50     ` Hemmann, Volker Armin
2006-03-24  8:16       ` 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=200603230856.24091.volker.armin.hemmann@tu-clausthal.de \
    --to=volker.armin.hemmann@tu-clausthal.de \
    --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®