devb-eide memory leak

QNX Newsgroups (Archives) qdn.public.qnxrtp.os
1

I am running QNX 6.2.1 on a single board computer with only 4Mb of RAM. The
problem is that devb-eide slowly expands as I access the drive until it
fills up all the free memory.

I start it in the .boot file as:
devb-eide blk automount=hd0t77:/:qnx4,cache=50k,alloc=0 &

Is there another option I should be using to limit it’s size?

Thanks
Larry Holding

2

“Ansys” <ansys@ansys.co.za> wrote in message
news:b9tevn$35f$1@inn.qnx.com…

I am running QNX 6.2.1 on a single board computer with only 4Mb of RAM.
The
problem is that devb-eide slowly expands as I access the drive until it
fills up all the free memory.

I start it in the .boot file as:
devb-eide blk automount=hd0t77:/:qnx4,cache=50k,alloc=0 &

Is there another option I should be using to limit it’s size?

Look at alloc option.

Thanks
Larry Holding

3

Ansys <ansys@ansys.co.za> wrote:

I am running QNX 6.2.1 on a single board computer with only 4Mb of RAM. The
problem is that devb-eide slowly expands as I access the drive until it
fills up all the free memory.

Really? Or do you mean the data size grows a little bit more than the
expected 50k (4MB isn’t all that much to claim a “memory leak” under)?

I start it in the .boot file as:
devb-eide blk automount=hd0t77:/:qnx4,cache=50k,alloc=0 &
Is there another option I should be using to limit it’s size?

Don’t set “alloc=”. Set “cache=” and “vnode=” to small values (if
you only have a 50k cache try 32 vnodes, but be prepared for ENFILE),
and all other caches will automatically re-scale themselves down based
on those settings. Youd could also explicitly disable the “map=” and
“ncache=” caches (but performance will suffer). Refer to the messaage
from “use /lib/dll/io-blk.so” …