On Tue, 2009-11-17 at 21:51 +0900, Minchan Kim wrote: > I think it's because mempool reserves memory. > (# of I/O issue\0 is hard to be expected. > How do we determine mempool size of each block driver? > For example, maybe, server use few I/O for nand. > but embedded system uses a lot of I/O. No, you scale the mempool to the minimum amount required to make progress -- this includes limiting the 'concurrency' when handing out mempool objects. If you run into such tight corners often enough to notice it, there's something else wrong. I fully agree with ripping out PF_MEMALLOC from pretty much everything, including the VM, getting rid of the various abuse outside of the VM seems like a very good start. -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
