mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Merillat <dan.merillat@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
	linux-kernel@vger.kernel.org,
	Norbert Preining <preining@logic.at>,
	Tomasz Chmielewski <mangoo@wpkg.org>,
	Sven-Haegar Koch <haegar@sdinet.de>,
	Dave Chinner <david@fromorbit.com>
Subject: Re: Linux 2.6.31 - very swap-happy with plenty of free RAM
Date: Wed, 2 Dec 2009 23:16:02 -0500	[thread overview]
Message-ID: <c0c067900912022016u32e393cw3fe9e04ba1051253@mail.gmail.com> (raw)
In-Reply-To: <4B0DDFDA.1030905@redhat.com>

>
> Can you try out the patch from
> http://lkml.org/lkml/2009/11/25/467 ?

It's on the system now, I missed your reply for some reason.   Stupid gmail.

So far it's survived the 'open all in tabs' firefox test, which used
to throw it into complete disarray, threw a 1gb file into tmpfs and it
swapped out 150mb and didn't trash.

It's running all the things I normally do in a day all at once, so far
nothing, but it seems to take
a while before things go pear-shaped.

I'll give another update in a day or so.

As an aside, why is swapin so incredibly slow compared to swapout?   I
mean, I understand why (pagefault->swapin *wait* run process new
pagefault->swapin etc) but wouldn't much larger (4mb?) granularity of
swap help with modern high-speed drives?

I've seen a high of 2mb/sec swapin, and 100+mb/sec swapout.

swapoff /dev/swap shows this very clearly - theoretically it should be
"drop enough clean pages to fit everything into RAM, then read the
swap partition in linearly".  It's especially egregious in the case
where a memory-hog has terminated, leaving more free RAM than swapped
pages and swapoff still takes upwards of 10 minutes to complete what
should be a 2-second disk read.

  reply	other threads:[~2009-12-03  4:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05  1:16 complete IO hang since a few kernel revision Norbert Preining
2009-10-05  2:57 ` Ulrich Lukas
2009-10-05  8:33   ` Norbert Preining
2009-10-06  2:00     ` Robert Hancock
2009-10-06  2:05       ` Norbert Preining
2009-10-06  7:11     ` Mike Galbraith
2009-10-06  7:16       ` Norbert Preining
2009-10-06  7:44         ` Mike Galbraith
2009-10-10 19:06           ` Petr Titěra
2009-11-18  7:56 ` Linux 2.6.31 - very swap-happy with plenty of free RAM Dan Merillat
2009-11-18 15:22   ` Rik van Riel
2009-11-18 15:48   ` Norbert Preining
2009-11-19 14:36   ` KOSAKI Motohiro
2009-11-25 23:13     ` Dan Merillat
2009-11-26  1:54       ` Rik van Riel
2009-12-03  4:16         ` Dan Merillat [this message]
2009-12-07 20:49           ` Dan Merillat
2009-12-09 20:48             ` Henrique de Moraes Holschuh
2009-12-09 21:18               ` Rik van Riel
2009-11-18 21:45 Tomasz Chmielewski
2009-11-19  0:40 ` Dan Merillat
2009-11-19  1:09   ` Sven-Haegar Koch
2009-11-19  1:38     ` Dave Chinner
2009-11-19  6:43       ` Tomasz Chmielewski
2009-11-23 21:57         ` Dan Merillat
2009-11-27  1:56   ` Bill Davidsen

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=c0c067900912022016u32e393cw3fe9e04ba1051253@mail.gmail.com \
    --to=dan.merillat@gmail.com \
    --cc=david@fromorbit.com \
    --cc=haegar@sdinet.de \
    --cc=kosaki.motohiro@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mangoo@wpkg.org \
    --cc=preining@logic.at \
    --cc=riel@redhat.com \
    /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®