Page pool... yep. It's on the todo list, but I'm not even fully comfortable with the basic Rom Kitchen. Sheesh we have to crawl before we can fly
And the page pool at 8mb is probably pretty good
Quote:
The Page Pool
Applications use RAM in two ways. There is code that runs, and there is data that is created while it is running. On a NOR device, the code can run directly from the ROM and not be loaded into RAM first. This process is called XIP (eXecute In Place). NAND devices can't XIP, so their code is loaded into RAM and executed from there. If you don't have a Page Pool, this code is loaded into normal RAM. The Page Pool is a mechanism to limit how much code is loaded into normal RAM. With a Page Pool, we can unload code that hasn't been used in a while and reload it later if we need to. We can't do that without a Page Pool.
On a typical NAND-based WM5 device, the Page Pool is 4.5M.
|
So - page pool is used like normal RAM to run programs, and the OS as well... it's almost like shared memory of sorts.
If you pull memory out of general RAM and allocate it to the page pool, it would seem like its still used for exactly the same thing. So what's the advantage to having it be in the page pool???