Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fabric/av: Introduce FI_SOURCE_ERR flag #2811

Merged
merged 1 commit into from Mar 20, 2017
Merged

fabric/av: Introduce FI_SOURCE_ERR flag #2811

merged 1 commit into from Mar 20, 2017

Conversation

shefty
Copy link
Member

@shefty shefty commented Mar 15, 2017

This flag requires that the provider report the raw
address data for any address that is received which is not
already inserted into the local AV.

Signed-off-by: Sean Hefty sean.hefty@intel.com

This flag requires that the provider report the raw
address data for any address that is received which is not
already inserted into the local AV.

Signed-off-by: Sean Hefty <sean.hefty@intel.com>
were not inserted into the AV. This allows the provider to optimize
the reporting of the source fi_addr_t without the overhead of
verifying whether the address is in the AV. If full address
validation is necessary, FI_SOURCE_ERR must be used.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this fi_addr_t may not be inserted in any AV? Will this still get released when the AV is closed?

raw source addressing data be returned as part of completion data
for any address that has not been inserted into the local address
vector. Use of this capability may require the provider to
validate incoming source address data against addresses stored in
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it more of a lookup than a validate?

@shefty
Copy link
Member Author

shefty commented Mar 15, 2017 via email

@bturrubiates
Copy link
Member

The fi_addr_t is just a 64-bit value, so there's nothing to remove from the AV. No adjustments are made to the AV. This just documents that the provider may be forming the fi_addr_t values directly from the source address (like reporting a sockaddr_in as the fi_addr_t).

Well, the fi_addr_t could be a pointer to some heap-allocated structure.

@shefty
Copy link
Member Author

shefty commented Mar 15, 2017 via email

@shefty shefty merged commit a72c3e3 into ofiwg:master Mar 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants