On 05/16/2012 12:18 AM, Konrad Rzeszutek Wilk wrote: >>>> I think it's not urgent than zs_handle mess. >>> >>> I am having a hard time parsing that. Are you saying that >>> this is not as important as the zs_handle fixup? I think >>> that is what you meant, but what to make sure. >> >> >> Yes. I think zs_hande fixup is top priority for me than any other stuff I pointed out. > > What else is should we put on the TODO? Next I have a plan. 1. zs_handle zs_malloc(size_t size, gfp_t flags) - share a pool by many subsystem(like kmalloc) 2. zs_handle zs_malloc_pool(struct zs_pool *pool, size_t size) - use own pool(like kmem_cache_alloc) And there is severe another item but I think it's not good time to mention it because I don't have a big picture still yet. Only thing I can speak is that it's would be related to zram or zcache. I will compare which is better for me. I will tell it if I am ready. > > -- > To unsubscribe, send a message with 'unsubscribe linux-mm' in > the body to majordomo@xxxxxxxxx. For more info on Linux MM, > see: http://www.linux-mm.org/ . > Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ > Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a> > > > -- Kind regards, Minchan Kim -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>