[Peeweelinux] swapper prob.
Adi Linden
[email protected]
Mon, 18 Mar 2002 10:45:23 -0600 (CST)
Hi Mark,
My apologies. You're right. I should read messages more thoroughly before
replying. I understood his development system was complaining, not the
target.
The kernel parameter I was talking about is set by pwlconfig based on the
final ramdisk size. It is set for the target automatically.
The "ramdisk free" in pwlconfig changes the overall ramdisk size of the
target system. Since the ramdisk uses up physical memory, any change in
this paramter will change memory consumption on the target.
Adi
On Mon, 18 Mar 2002, Mark Meade wrote:
> Hi Adi,
>
> I'm a bit confused. I was under the impression that the "ramdisk free" parameter was used
> when Peewee determines the total ramdisk size.
>
> In one of the scripts, the formula seems to be
> total ram disk size = file system size + "free" size
>
> I tried playing with this parameter a few months ago, and from my notes:
>
> Filesystem 1k-blocks Used Free
> /dev/ram0 6764 4494 2270 (Ramdisk Free = 2000)
> /dev/ram0 5311 4494 817 (Ramdisk Free = 500)
>
> It seems like this parameter does affect the memory usage on the target. Am I
> misunderstanding something here?
>
> Thanks,
>
> Mark
>
> Adi Linden wrote:
>
> > I don't think the ramdisk paramter actually allocates any memory. It just
> > sets limits. I.e. I am running a box with 32MB of physical memory and the
> > remdisk paramter set to 200000, which would allow me a largest ramdisk of
> > 200MB.
>
>
>
>
> _______________________________________________
> Peeweelinux mailing list
> [email protected]
> http://mail.adis.on.ca/lists/listinfo/peeweelinux
>