I think in the embedded system always use "mem=" parameter to boot
kernel and reserve a continuous memory then provide for some device
use as their private "buffer",like io-mem remap in the kernel space to
use.
BRs
Lin
2009/3/31 Peter Teoh :
> On Tue, Mar 31, 2009 at 11:11 AM, Peter Chen wrote:
On Tue, Mar 31, 2009 at 11:11 AM, Peter Chen wrote:
> Thank you, peter.
> Yes, graphical guys ask me the same questions, and the other device drivers
> which don't support scatter buffer also have this doubt.
>
>
but i suspect it could be easily achieved through a patch to the
kernel, to keep sta
Thank you, peter.
Yes, graphical guys ask me the same questions, and the other device
drivers which don't support scatter buffer also have this doubt.
Best Regards,
Peter Chen
On Mon, 2009-03-30 at 11:53 -0400, Peter Teoh wrote:
> On Mon, Mar 30, 2009 at 8:13 AM, Peter Chen wrote:
> > Hi all,
On Mon, Mar 30, 2009 at 8:13 AM, Peter Chen wrote:
> Hi all,
>
> I have two questions about alloc continual physical memory, hope you can
> give me some tips.
>
> 1. How biggest continual physical memory the kernel can be ensured to give
> during the kernel running?
> 2. What is the threshold valu
I'm not sure about Linux (and am curious) but in C this is defined by the
heap size.
The heap normally is located between the end of (i)data and the lowest the
stack(s) can/might go (assuming a full descending stack).
This is decided at link time and is runtime constant.
Also note that - regardles
Hi all,
I have two questions about alloc continual physical memory, hope you can
give me some tips.
1. How biggest continual physical memory the kernel can be ensured to
give during the kernel running?
2. What is the threshold value for alloc_page and kmalloc?
This memory is demanded to alloc d
