From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Abu M. Muttalib" <abum@aftek.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
chase.venters@clientec.com, kernelnewbies@nl.linux.org,
linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm <linux-mm@kvack.org>
Subject: RE: Commenting out out_of_memory() function in __alloc_pages()
Date: Sun, 09 Jul 2006 13:09:57 +0100 [thread overview]
Message-ID: <1152446997.27368.52.camel@localhost.localdomain> (raw)
In-Reply-To: <BKEKJNIHLJDCFGDBOHGMAEFDDCAA.abum@aftek.com>
Ar Sul, 2006-07-09 am 17:18 +0530, ysgrifennodd Abu M. Muttalib:
> but I am running the application on an embedded device and have no swap..
> what do I need to do in this case??
Use less memory ?
You can play with /proc/sys/vm/overcommit_ratio. That is set at 50%
which is usually a good safe value with swap. If you know the kernel and
kernel memory will be 20% of memory worst case you can set it to 80 and
so on.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Abu M. Muttalib" <abum@aftek.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
chase.venters@clientec.com, kernelnewbies@nl.linux.org,
linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm <linux-mm@kvack.org>
Subject: RE: Commenting out out_of_memory() function in __alloc_pages()
Date: Sun, 09 Jul 2006 13:09:57 +0100 [thread overview]
Message-ID: <1152446997.27368.52.camel@localhost.localdomain> (raw)
In-Reply-To: <BKEKJNIHLJDCFGDBOHGMAEFDDCAA.abum@aftek.com>
Ar Sul, 2006-07-09 am 17:18 +0530, ysgrifennodd Abu M. Muttalib:
> but I am running the application on an embedded device and have no swap..
> what do I need to do in this case??
Use less memory ?
You can play with /proc/sys/vm/overcommit_ratio. That is set at 50%
which is usually a good safe value with swap. If you know the kernel and
kernel memory will be 20% of memory worst case you can set it to 80 and
so on.
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Abu M. Muttalib" <abum@aftek.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
chase.venters@clientec.com, kernelnewbies@nl.linux.org,
linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm <linux-mm@kvack.org>
Subject: RE: Commenting out out_of_memory() function in __alloc_pages()
Date: Sun, 09 Jul 2006 13:09:57 +0100 [thread overview]
Message-ID: <1152446997.27368.52.camel@localhost.localdomain> (raw)
In-Reply-To: <BKEKJNIHLJDCFGDBOHGMAEFDDCAA.abum@aftek.com>
Ar Sul, 2006-07-09 am 17:18 +0530, ysgrifennodd Abu M. Muttalib:
> but I am running the application on an embedded device and have no swap..
> what do I need to do in this case??
Use less memory ?
You can play with /proc/sys/vm/overcommit_ratio. That is set at 50%
which is usually a good safe value with swap. If you know the kernel and
kernel memory will be 20% of memory worst case you can set it to 80 and
so on.
--
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>
next prev parent reply other threads:[~2006-07-09 12:09 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.AmXizdwfdZtqgKFSMcRp3U0QZXI@ifi.uio.no>
2006-07-08 18:06 ` Commenting out out_of_memory() function in __alloc_pages() Robert Hancock
2006-07-08 18:06 ` Robert Hancock
2006-07-09 4:23 ` Abu M. Muttalib
2006-07-09 4:23 ` Abu M. Muttalib
2006-07-09 4:23 ` Abu M. Muttalib
2006-07-09 5:18 ` Chase Venters
2006-07-09 5:18 ` Chase Venters
2006-07-09 5:18 ` Chase Venters
2006-07-09 6:11 ` Abu M. Muttalib
2006-07-09 6:11 ` Abu M. Muttalib
2006-07-09 6:11 ` Abu M. Muttalib
2006-07-09 7:55 ` Chase Venters
2006-07-09 7:55 ` Chase Venters
2006-07-09 7:55 ` Chase Venters
2006-07-09 11:55 ` Alan Cox
2006-07-09 11:55 ` Alan Cox
2006-07-09 11:48 ` Abu M. Muttalib
2006-07-09 11:48 ` Abu M. Muttalib
2006-07-09 11:48 ` Abu M. Muttalib
2006-07-09 12:01 ` Willy Tarreau
2006-07-09 12:01 ` Willy Tarreau
2006-07-09 12:01 ` Willy Tarreau
2006-07-09 12:13 ` Abu M. Muttalib
2006-07-09 12:13 ` Abu M. Muttalib
2006-07-09 12:13 ` Abu M. Muttalib
2006-07-09 12:15 ` Willy Tarreau
2006-07-09 12:15 ` Willy Tarreau
2006-07-09 12:15 ` Willy Tarreau
2006-07-09 13:12 ` Abu M. Muttalib
2006-07-09 13:12 ` Abu M. Muttalib
2006-07-09 13:12 ` Abu M. Muttalib
2006-07-09 13:23 ` Willy Tarreau
2006-07-09 13:23 ` Willy Tarreau
2006-07-09 13:23 ` Willy Tarreau
2006-07-09 12:09 ` Alan Cox [this message]
2006-07-09 12:09 ` Alan Cox
2006-07-09 12:09 ` Alan Cox
2006-07-09 12:03 ` Abu M. Muttalib
2006-07-09 12:03 ` Abu M. Muttalib
2006-07-09 12:03 ` Abu M. Muttalib
2006-07-09 12:03 ` Nick Piggin
2006-07-09 12:03 ` Nick Piggin
2006-07-09 12:03 ` Nick Piggin
2006-07-09 14:34 ` Abu M. Muttalib
2006-07-09 14:34 ` Abu M. Muttalib
2006-07-09 14:34 ` Abu M. Muttalib
2006-07-09 15:15 ` Nick Piggin
2006-07-09 15:15 ` Nick Piggin
2006-07-09 15:15 ` Nick Piggin
2006-07-07 9:46 Abu M. Muttalib
2006-07-07 9:46 ` Abu M. Muttalib
2006-07-07 9:54 ` Robin Holt
2006-07-07 9:54 ` Robin Holt
2006-07-07 9:54 ` Robin Holt
2006-07-11 14:57 ` Abu M. Muttalib
2006-07-11 14:57 ` Abu M. Muttalib
2006-07-11 14:57 ` Abu M. Muttalib
2006-07-11 15:08 ` Abu M. Muttalib
2006-07-11 15:08 ` Abu M. Muttalib
2006-07-11 15:08 ` Abu M. Muttalib
2006-07-11 15:19 ` Abu M. Muttalib
2006-07-11 15:19 ` Abu M. Muttalib
2006-07-11 15:19 ` Abu M. Muttalib
2006-07-13 5:12 ` Mouhammad Tayseer Alquoatli
2006-07-11 15:35 ` Chase Venters
2006-07-11 15:35 ` Chase Venters
2006-07-11 15:35 ` Chase Venters
2006-07-11 19:57 ` Al Boldi
2006-07-24 9:44 ` Abu M. Muttalib
2006-07-24 9:44 ` Abu M. Muttalib
2006-07-24 9:44 ` Abu M. Muttalib
2006-07-07 21:21 ` Chase Venters
2006-07-07 21:21 ` Chase Venters
2006-07-07 21:21 ` Chase Venters
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=1152446997.27368.52.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=abum@aftek.com \
--cc=chase.venters@clientec.com \
--cc=hancockr@shaw.ca \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-newbie@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 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.