[Ofvwg] Meeting notes - 7/7/2015

[Shamis, Pavel]

I prepared a google doc that we can use for summarizing existing error codes and proposing new codes:
https://docs.google.com/spreadsheets/d/143rPK7a7Df1uY0rF9Bq6mabhpxbp--Fo9-poPCDQYag/edit?usp=sharing

Feel free to update.

Best,
Pavel (Pasha) Shamis
---
Computer Science Research Group
Computer Science and Math Division
Oak Ridge National Laboratory






On Jul 7, 2015, at 3:20 PM, Liran Liss <liranl at mellanox.com>
 wrote:

> Pasha raised the issue of inconsistent error codes in Verbs.
> Several API calls were reviewed.
> 
> Examples for inconsistency:
> - Using the same error code for multiple error types
> - Inconsistency among providers
> - Inconsistent use of -1 and errno codes in return values
> 
> Additional issues:
> - Are errno codes descriptive enough?
> - If not, how do we introduce new codes? Extend the errno range? New enums? Other?
> - Can we change the error scheme without breaking compatibility? Is this a new feature?
> -- Runtime vs. compile-time compatibility
> 
> To do:
> - Get user input on compatibility. Is anyone relying on specific providers?
> - Get user input on POSIX vs. other error schemes
> - Prepare a comparison table for each API:
> -- Current practice by providers
> -- Error semantics indicated by the specification
> -- Mapping to errno codes
> -- Mapping to extended codes
> 
> --Liran
> 
> _______________________________________________
> ofvwg mailing list
> ofvwg at lists.openfabrics.org
> http://lists.openfabrics.org/mailman/listinfo/ofvwg
>