From: Roland Dreier <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [ANNOUNCE] libmlx4 1.0.5 is released
Date: Thu, 30 May 2013 11:18:55 -0700 [thread overview]
Message-ID: <1369937935-21981-1-git-send-email-roland@kernel.org> (raw)
libmlx4 is a userspace driver for Mellanox ConnectX InfiniBand/IBoE
HCAs. It is a plug-in module for libibverbs that allows programs to
use Mellanox hardware directly from userspace.
A new stable release is available from
http://www.openfabrics.org/downloads/mlx4/libmlx4-1.0.5.tar.gz
with sha1sum
15356e0dfe78f98bf2586c3fa0058b0be6ecfa4f libmlx4-1.0.5.tar.gz
I also pushed the latest tree and tag out to kernel.org:
git://git.kernel.org/pub/scm/libs/infiniband/libmlx4.git
(the name of the tags is libmlx4-1.0.5)
The main new features of this release are support for 64-byte CQEs
(when turned on in the mlx4_core kernel driver via the
enable_64b_cqe_eqe module parameter) and support for raw QPs.
The git shortlog since libmlx4 1.0.4 is:
Dotan Barak (5):
Replace sscanf() with strtol()
Allow using the whole Blue Flame buffer
Use BlueFlame for RDMA Write [with immediate] without data
Change enumeration names for masked atomic opcodes
Have ibv_modify_qp() return right value when ibv_query_port() fails
Or Gerlitz (2):
Add support for 64B CQEs
Add raw packet QP support
Roland Dreier (4):
Rename configure.in -> configure.ac
Use autoreconf in autogen.sh
configure: Minor updates suggested by autoupdate
Roll libmlx4 1.0.5 release
--
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:[~2013-05-30 18:18 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=1369937935-21981-1-git-send-email-roland@kernel.org \
--to=roland-dgejt+ai2ygdnm+yrofe0a@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