All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Johannes Stezenbach <js@sig21.net>
Cc: "Hillf Danton" <dhillf@gmail.com>,
	"Toralf Förster" <toralf.foerster@gmx.de>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: swap storm since kernel 3.2.x
Date: Thu, 09 Feb 2012 09:06:41 -0500	[thread overview]
Message-ID: <4F33D2F1.5000606@redhat.com> (raw)
In-Reply-To: <20120209135407.GA15492@sig21.net>

On 02/09/2012 08:54 AM, Johannes Stezenbach wrote:
> On Thu, Feb 09, 2012 at 02:21:55PM +0100, Johannes Stezenbach wrote:
>> it looks good.  Neither do I get the huge debug_objects_cache
>> nor does it swap, after running a crosstool-ng toolchain build.
>> Well, last time I also had one kvm -m 1G instance running.  I'll
>> try if that triggers the issue.  So far:
>
> The kvm produced a bunch of page allocation failures
> on the host:

> (repeats a few times)
>
> I guess that is expected with your patch?

That is indeed why my patch series was significantly larger
than Hillf's little test patch :)

-- 
All rights reversed

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Johannes Stezenbach <js@sig21.net>
Cc: "Hillf Danton" <dhillf@gmail.com>,
	"Toralf Förster" <toralf.foerster@gmx.de>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: swap storm since kernel 3.2.x
Date: Thu, 09 Feb 2012 09:06:41 -0500	[thread overview]
Message-ID: <4F33D2F1.5000606@redhat.com> (raw)
In-Reply-To: <20120209135407.GA15492@sig21.net>

On 02/09/2012 08:54 AM, Johannes Stezenbach wrote:
> On Thu, Feb 09, 2012 at 02:21:55PM +0100, Johannes Stezenbach wrote:
>> it looks good.  Neither do I get the huge debug_objects_cache
>> nor does it swap, after running a crosstool-ng toolchain build.
>> Well, last time I also had one kvm -m 1G instance running.  I'll
>> try if that triggers the issue.  So far:
>
> The kvm produced a bunch of page allocation failures
> on the host:

> (repeats a few times)
>
> I guess that is expected with your patch?

That is indeed why my patch series was significantly larger
than Hillf's little test patch :)

-- 
All rights reversed

  reply	other threads:[~2012-02-09 14:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 10:09 swap storm since kernel 3.2.x Toralf Förster
2012-02-04 13:33 ` Johannes Stezenbach
2012-02-04 14:36   ` Toralf Förster
2012-02-05  4:45     ` Hillf Danton
2012-02-05  4:45       ` Hillf Danton
2012-02-05 10:07       ` Toralf Förster
2012-02-05 10:07         ` Toralf Förster
2012-02-05 11:38         ` Hillf Danton
2012-02-05 11:38           ` Hillf Danton
2012-02-08  8:56           ` Toralf Förster
2012-02-08  8:56             ` Toralf Förster
2012-02-08 11:52             ` Johannes Stezenbach
2012-02-08 11:52               ` Johannes Stezenbach
2012-02-08 12:34               ` Hillf Danton
2012-02-08 12:34                 ` Hillf Danton
2012-02-09 11:36                 ` Johannes Stezenbach
2012-02-09 11:36                   ` Johannes Stezenbach
2012-02-09 12:02                   ` Hillf Danton
2012-02-09 12:02                     ` Hillf Danton
2012-02-09 13:21                     ` Johannes Stezenbach
2012-02-09 13:21                       ` Johannes Stezenbach
2012-02-09 13:54                       ` Johannes Stezenbach
2012-02-09 13:54                         ` Johannes Stezenbach
2012-02-09 14:06                         ` Rik van Riel [this message]
2012-02-09 14:06                           ` Rik van Riel
2012-02-10 12:36                           ` Hillf Danton
2012-02-10 12:36                             ` Hillf Danton
2012-02-09 13:04                   ` Toralf Förster
2012-02-09 13:04                     ` Toralf Förster

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=4F33D2F1.5000606@redhat.com \
    --to=riel@redhat.com \
    --cc=dhillf@gmail.com \
    --cc=js@sig21.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=toralf.foerster@gmx.de \
    /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.