Re: 2.2/2.4/2.6 VMs: do malloc() ever return NULL?
From: William Lee Irwin III (wli_at_holomorphy.com)
Date: 11/26/03
- Previous message: Ihar 'Philips' Filipau: "Re: 2.2/2.4/2.6 VMs: do malloc() ever return NULL?"
- In reply to: Ihar 'Philips' Filipau: "Re: 2.2/2.4/2.6 VMs: do malloc() ever return NULL?"
- Next in thread: Richard B. Johnson: "Re: 2.2/2.4/2.6 VMs: do malloc() ever return NULL?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 26 Nov 2003 06:36:35 -0800 To: Ihar 'Philips' Filipau <filia@softhome.net>
On Wed, Nov 26, 2003 at 03:33:06PM +0100, Ihar 'Philips' Filipau wrote:
> How can I tell the limit of the RAM which can be locked?
> My test had shown that single application can lock 112MB of RAM, but
> fails to lock 128MB of RAM. (I have 256MB phy RAM - We just cannot find
> smaller memory modules on market in any way :-))
> Is it limited to less than half of physical RAM?
> This would be Ok for me in any way.
The limit should be available RAM.
-- wli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
- Previous message: Ihar 'Philips' Filipau: "Re: 2.2/2.4/2.6 VMs: do malloc() ever return NULL?"
- In reply to: Ihar 'Philips' Filipau: "Re: 2.2/2.4/2.6 VMs: do malloc() ever return NULL?"
- Next in thread: Richard B. Johnson: "Re: 2.2/2.4/2.6 VMs: do malloc() ever return NULL?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
