"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."
this quote was taken from:
http://blogs.msdn.com/windowsmobile/...17/494177.aspx
i thought it was a pretty good explanation. if you're curious the article gets into the dma buffer, radio stack etc., and how they affect device memory.
i've always thought of the page pool in wm to be comparable to the swap partition on a linux system, or virtual memory in windows. please set me straight if i'm crooked.
hope it helps.