man/fi_getinfo.3: Clean up return values section

Fix typo in description of fi_dupinfo() error return.
Clarify that first paragraph refers to fi_getinfo().

Fixes #259

Signed-off-by: Patrick MacArthur <pmacarth@iol.unh.edu>
add fi_no_enable since passive endpoints do not need enable
(at least its not called in the example programs)

Signed-off-by: Reese Faucette <rfaucett@cisco.com>
Merge pull request #304 from rfaucett/pr/fi_no_enable

add fi_no_enable since passive endpoints do not need enable
usnic: various updates
- start work on SW emulation of reliable messaging
- make async address resolution native
- move progression thread from domain to fabric
- add open_ops for fabric and AV

Signed-off-by: Reese Faucette <rfaucett@cisco.com>
Merge pull request #306 from rfaucett/pr/usdf_rc

usnic: various updates
fabric: Add mode bits to RX/TX attributes

When an RX/TX context is opened, an application can
specify a subset of the capabilities requested of the
endpoint.  As a result, the provider may be able to
provide relaxed mode bits.

For example, an endpoint that supports both tagged
messages and RMA operations may require FI_CONTEXT
mode bits.  However, a TX context that will only be
used for RMA may not require this mode.  By removing
this mode, an application may see improved performance
when using the RMA TX without needing to allocate
fi_context structures.

Signed-off-by: Sean Hefty <sean.hefty@intel.com>
Merge pull request #309 from patrickmacarthur/dupinfo-man-fix

man/fi_getinfo.3: Clean up return values section
man/fi_errno: Add man page that describes list of errors

Provide a man page that defines possible fabric errors and
their general meaning.

Signed-off-by: Sean Hefty <sean.hefty@intel.com>
fabric: Define FI_NOCQ

Now that the CQ was spun off the EQ, define FI_NOCQ,
similar to FI_NOEQ.

Signed-off-by: Sean Hefty <sean.hefty@intel.com>
README.md: first cut at a set of information for the Github project page
README.md: fix a typo
fabric: Define FI_COMPLETION

Rather than using FI_EVENT to indicate that a completion
should be generated for a given operation, allow the user
to specify this using FI_COMPLETION.  FI_COMPLETION is
defined with the same value as FI_EVENT to avoid using
another flag bit and allow either value to be used.

Signed-off-by: Sean Hefty <sean.hefty@intel.com>
Merge pull request #311 from shefty/master

Mostly unrelated set of changes