RE: [Sandiaportals-devel] Strangeness in event fields

[Jared R. <ja...@cr...>]

> Interesting... I never thought of doing this.  The spec doesn't
> explicitly state that PtlMDUpdate resets an MD's local offset
> but maybe
> it should.  Do you have a good reason for wanting to doing this?

It's just a way to wake up an MD without creating a new one, once it's data
is no longer cared about.  I think the offset has to be reset, since the API
md structure can't keep this information itself, and PtlMDUpdate doesn't
really care that the new md happens to be at the same starting address as
the old one.  I'm pretty sure the problem would still manifest itself even
if you were to unlink the MD and reattach it into the match list, since the
problem appears to be in the md structure data, not in MDUpdate.  One
possible use for that might be keeping a chain of MDs on a single matchlist
so that incoming messages don't get dropped when one MD fills, then being
able to reattach the MD at the end of the list without having to worry about
which particular MD we are referring to.

> Yes, this is definitely a bug.  Are you using the HEAD?  Or are you
> using Cray Portals?

Cray.

>
> This is a bug also.  The api-side should be translating
> lib-side handle
> to the api-side handle before revealing it to you.
>
> I can take a stab at fixing these problems.  Do you have a
> test program
> handy?
>

Yes, I'll send them to you in a separate mail.

--Jared