On Fri, 15 Feb 2008, Caitlin Bestler wrote: > There isn't much point in the RDMA layer subscribing to mmu > notifications > if the specific RDMA device will not be able to react appropriately when > the notification occurs. I don't see how you get around needing to know > which devices are capable of supporting page migration (via > suspend/resume > or other mechanisms) and which can only respond to a page migration by > aborting connections.
You either register callbacks if the device can react properly or you dont. If you dont then the device will continue to have the problem with page pinning etc until someone comes around and implements the mmu callbacks to fix these issues. I have doubts regarding the claim that some devices just cannot be made to suspend and resume appropriately. They obviously can be shutdown and so its a matter of sequencing the things the right way. I.e. stop the app wait for a quiet period then release resources etc. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
