> > My program need to a 32M buffer, so I add "append="mem=96M"" to lilo.conf,
> > then the PC only know 96M mem, I can use the rest 32M. Following is a
> > simple example:
>
> No!!! You may stomp on regions reserved by the motherboard.
>
> Unless you must deal with stupid DMA hardware, just use
> man 2 mlock
>
> On Sat, 21 Oct 2000, Zhixu Liu wrote:
> >
> > But now, question
> > is if I want to reserve some RAM for program use, how can I do? Thanks for
> > your help.
> >
After I use mlock, how can I know the memory I malloced is in RAM? Tha
On Sat, 21 Oct 2000, Cefiar wrote:
> At 08:24 PM 20/10/00 -0400, Zhixu Liu wrote:
> >My PC have 128M RAM, but in /proc/meminfo, it display 122424K, not
> >128*1024K = 131072K, what does this mean?
>
> Sounds like something is stealing your ram.
>
> Usual suspec
Hi, all:
My PC have 128M RAM, but in /proc/meminfo, it display 122424K, not
128*1024K = 131072K, what does this mean?
My program need to a 32M buffer, so I add "append="mem=96M"" to lilo.conf,
then the PC only know 96M mem, I can use the rest 32M. Following is a
simple example:
/**
> > I have a question about the time-slice of linux, how do I know it, or how
> > can I test it?
>
> First look for the (platform-specific) definition of HZ in
> include/asm/param.h. This is how many timer interrups you get per second (eg
> on i386 it's 100). Then look at include/linux/sched.h fo
Hi, All:
I have a question about the time-slice of linux, how do I know it, or how
can I test it?
Thanks for you help.
Zhixu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
6 matches
Mail list logo