Great news! I have taken over Dean's xpmem patch set while he is on sabbatical. Before he left, he had his patch mostly working on top of this patch set. We had one deadlock. I have coded for that specific deadlock and xpmem now passes a simple grant/attach/fault/fork/unmap/map test.
After analyzing it, I believe we still have a nearly related deadlock which will require some refactoring of code. I am certain that the same mechanism I used for this deadlock break will work in that case, but it will require too many changes for me to finish this weekend. For our customer base, this case, in the past, has resulted in termination of the application and our MPI library specifically states that this mode of operation is not permitted, so I think we will be able to pass their regression tests. I will need to coordinate that early next week. The good news, at this point, Christoph's version 5 of the mmu_notifiers appears to work for xpmem. The mmu_notifier call-outs where the in_atomic flag is set still result in a BUG_ON. That is not an issue for our normal customer as our MPI already states this is not a valid mode of operation and provides means to avoid those types of mappings. Thanks, Robin -- 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/
