All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: Re: Memory management woes - order 1 allocation failures
Date: Fri, 26 Feb 2010 13:24:07 +0100	[thread overview]
Message-ID: <201002261324.08078.elendil@planet.nl> (raw)
In-Reply-To: <201002261232.28686.elendil@planet.nl>

On Friday 26 February 2010, Frans Pop wrote:
> As can be seen from the attached munin graph [1] the system has only 256
> MB memory, but that's quite normal for a simple NAS system.

Oops. Make that "only 128 MB".

WARNING: multiple messages have this Message-ID (diff)
From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: Re: Memory management woes - order 1 allocation failures
Date: Fri, 26 Feb 2010 13:24:07 +0100	[thread overview]
Message-ID: <201002261324.08078.elendil@planet.nl> (raw)
In-Reply-To: <201002261232.28686.elendil@planet.nl>

On Friday 26 February 2010, Frans Pop wrote:
> As can be seen from the attached munin graph [1] the system has only 256
> MB memory, but that's quite normal for a simple NAS system.

Oops. Make that "only 128 MB".

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-02-26 12:24 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 11:32 Memory management woes - order 1 allocation failures Frans Pop
2010-02-26 12:24 ` Frans Pop [this message]
2010-02-26 12:24   ` Frans Pop
2010-02-26 14:01 ` Pekka Enberg
2010-02-26 14:01   ` Pekka Enberg
2010-02-26 15:33   ` Frans Pop
2010-02-26 15:33     ` Frans Pop
2010-02-26 16:43     ` Christoph Lameter
2010-02-26 16:43       ` Christoph Lameter
2010-02-26 17:17       ` Pekka Enberg
2010-02-26 17:17         ` Pekka Enberg
2010-03-01  1:42         ` KOSAKI Motohiro
2010-03-01  1:42           ` KOSAKI Motohiro
2010-03-02 17:26           ` Mel Gorman
2010-03-02 17:26             ` Mel Gorman
2010-03-02 18:34             ` Alan Cox
2010-03-02 18:34               ` Alan Cox
2010-03-02 19:11               ` Mel Gorman
2010-03-02 19:11                 ` Mel Gorman
2010-03-02 19:29                 ` Greg KH
2010-03-02 19:29                   ` Greg KH
2010-03-02 21:16                   ` Mel Gorman
2010-03-02 21:16                     ` Mel Gorman
2010-03-02 22:17                     ` Alan Cox
2010-03-02 22:17                       ` Alan Cox
2010-03-02 22:29                       ` Mel Gorman
2010-03-02 22:29                         ` Mel Gorman
2010-03-12  3:32                         ` Frans Pop
2010-03-12  3:32                           ` Frans Pop
2010-03-02 23:31               ` KOSAKI Motohiro
2010-03-02 23:31                 ` KOSAKI Motohiro

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=201002261324.08078.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 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.