On 03/19/2015 10:59 PM, Dan Williams wrote: > > At least for block-i/o it seems the only place we really need struct > page infrastructure is for kmap(). Given we already need a kmap_pfn() > solution for option 2 a "dynamic allocation" stop along that > development path may just naturally fall out. Really? what about networked block-io, RDMA, FcOE emulated targets, mmaped pointers. virtual-machine bdev drivers Block layer sits in the middle of the stack not at the low end as you make it appear. There are lots of below the bio subsystems that tie into a page struct, which will now stop to operate, unless you do: pfn_to_page() which means a page-less pfn will now crash or will need to be rejected so any where you have a if (page_less_pfn()) ... /* Fail or do some other code like copy */ else page = pfn_to_page() Is a double code path in the Kernel and is a nightmare to maintain. (I'm here for you believe me ;-) ) Thanks Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
