On Sun, Apr 05, 2009 at 11:45:10PM -0700, Michael Rubin wrote: > Anyone have any comments? Or historical reasons? We operate with some > constrained memory situations, and were wondering if a patch to move > from kmalloc to vmalloc would be well received. Sorry, I didn't have time to get to this until now. I've been burning the midnight oil getting the e2fsprogs 1.41.5 release out, as well as catching up after the Collab Summit. The best thing to do I think is to try using kmalloc(), and if it fails, to fall back to vmalloc(). We can use is_vmalloc_addr() to decide whether to use vfree() or kfree(), a trick which I picked up from fs/ntfs/malloc.h. I'm surprised this trick isn't used more in the kernel. Perhaps there should be made a general-purpose infrastructure, but for now I'll just open-code it. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
