Actually this should only matter for dma buffers on kernel side and
for userspace not at all. A region of continous virtual memory can
consists of physically scattered memory without problems. That's what
the page table is for.
Bernhard
2010/3/10 Fabrizio Bertocci :
> Well,
> Im not an exper
Well,
Im not an expert of the kernel, but if I remember correctly, when the
system runs low in memory, the kernel doesn't necessarily kill the
process with higher memory use... and if fragmentation is really the
problem, the mjpg-streamer may have very little memory allocated
anyway...
I've seen th
> Although there is still enough free memory, probably the memory is
> entirely fragmented and it cannot allocate a large block?
What size of block does it need? I think it cannot be larger than one file
(~30...80k). I cannot imagine that it cannot be allocated. Or, if it occures,
only the mjpg-s
Although there is still enough free memory, probably the memory is
entirely fragmented and it cannot allocate a large block?
Does this problem occur regularly after about 300k frames?
In this case why don't you try to stop and restart mjpg-streamer right
before that just to see if the system stays
Hi,
I tried to use mjpg-streamer and it is working properly - except that after
recording ~30 frames (~6 hours recording) the kernel crashes. It kills all
processes with a strange "out of memory" message. I printed the memory info
about one minute before crash (date, cat /proc/meminfo, and
