On Mar 9, 2012, at 1:32 PM, Nathan Hjelm wrote:
> An mpool that is aware of local processes lru's will solve the problem in most cases (all that I have seen)
I agree -- don't let words in my emails make you think otherwise. I think this will fix "most" problems, but undoubtedly, some will still occur.
What's your timeline for having this ready -- should it go to 1.5.5, or 1.6?
More specifically: if it's immanent, and can go to v1.5, then the openib message is irrelevant and should not be used (and backed out of the trunk). If it's going to take a little bit, I'm ok leaving the message in v1.5.5 for now.
> but yes, we need to rework the pml to handle the remaining cases. There are two things that need to be changed (from what I can tell):
> 1) allow rget to fallback to send/put depending on the failure (I have fallback on put implemented in my branch-- and in my btl).
> 2) need to devise new criteria on when we should progress the rdma_pending list to avoid deadlock.
> #1 is fairly simple and I haven't given much though to #2.
> devel mailing list
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/