Hi,
I am using /dev/cmem module to allocate memory for the dsp algorithms.
My current cmem map looks like this

# insert cmemk, tell it to occupy physical 118MB-128MB (10M).
insmod cmemk.ko phys_start=0x87600000 phys_end=0x88000000
pools=1x3600000,5x829440,2x1244160,1x40960,2x8192

Yes, this is the default map that is specified in the dvsdk 2.0
release, i haven't changed it yet.
Now i want to make sure that the cmem can allocate atleast 16 buffers
of 829440 bytes as H.264 Main Profile can have a atmost 16 reference
frames for B-frames. I am dealing with a H.264 MP Level 3.0 decoder
(maximum resolution 720x576).

One way to achieve this is my simply increasing the cmem memory, so
that the module load line, for example, would look like this:

1.
# insert cmemk, tell it to occupy physical 109MB-128MB (19M).
insmod cmemk.ko phys_start=0x86D00000 phys_end=0x88000000
pools=1x3600000,16x829440,2x1244160,1x40960,2x8192

2.
The other way is to get rid of all other pools that are existing, and
keep only the 829440 bytes sized pool, eg.
# insert cmemk, tell it to occupy physical 115MB-128MB (13M).
insmod cmemk.ko phys_start=0x87300000 phys_end=0x88000000 pools=16x829440

At least currently i am not allocating buffers other than of size
829440, using CMEM, but at the same time i am not sure whether any of
the dsp algorithms allocated memory using CMEM (by guess would be no).
I would want this to be clarified, and whether it is safe to go with
the second option, as it allows better memory utilisation.

Please comment.
Regards
~Sameer
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to