public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	EWG <ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>
Subject: python-rdma v0.1 Release Announcement
Date: Tue, 15 Mar 2011 12:02:03 -0600	[thread overview]
Message-ID: <20110315180203.GD12991@obsidianresearch.com> (raw)

I am pleased to announce the initial release of `python-rdma` a
package to provide a Python API for the Linux RDMA stack. This initial
release is mainly focused on IB specific management APIs, but the
package also covers ibverbs.

A new API was developed for this library that is designed to take
advantage of Python features and provides a very uniform, integrated
design across all the different aspects of IB and RDMA programming. It
has a particular focus on ease of use and correct operation of the IB
and RDMA protocol stacks.

Included is a re-implementation of a substantial portion of the
`infinband-diags` package. This re-implementation is functionally very
similar to `infiniband-diags` but also gains a number of new features:

- Uniform end port addressing. All commands support GID, port GUID,
  LID and DR path, even commands that are GMP based (like perfquery).
- Support for collecting information entirely from the SA via the
  `--sa` option.
- Consistently fetches path records for GMP communication (eg in
  perfquery) to support topologies with special requirements.
- Extensive MAD parallelization provides very good performance.
- All commands support a discovery cache file, which stores
  information in an efficient binary format.
- Much better debugging, including packet tracing down to full field decode.
- Minor new features to many tools, review section 8 of the manual for
  details.

The library itself is intended mainly for applications where quick
development is more important that the highest performance, such as:

- IB manamagent software development
- RDMA test development
- Training and problem exploration

Although already quite complete there are a few obvious areas that I
hope to have finished in the future:

- Integration of IB and RDMA CMs
- Support for RMPP when using verbs to issue GMPs - this will enable
  all diags to function in `--sa` mode without access to /dev/umad.
- Completion of missing `infinband-diags` commands

It is my hope this work will be of use to the wider InfiniBand community.

Extensive prebuilt documentation for the module can be reviewed online
<http://www.obsidianresearch.com/python-rdma/doc/index.html>, and the
source code is available on GitHub <http://github.com/jgunthorpe/python-rdma>.

I'm planning to give a short presentation on this library at the
forthcoming Monterey workshop, see you all there!

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

                 reply	other threads:[~2011-03-15 18:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110315180203.GD12991@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox