From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: libibverbs-1.2.0-rc1 release
Date: Wed, 23 Sep 2015 13:02:57 -0400 [thread overview]
Message-ID: <5602DB41.5070700@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]
I have done a pre-release of the upcoming libibverbs-1.2.0 release. The
code has been pushed to the official git repo and also an -rc1 tarball
uploaded to the https://ww.openfabrics.org/downloads/verbs download
area. From the tag message:
tag libibverbs-1.2.0-rc1
Tagger: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date: Wed Sep 23 12:47:04 2015 -0400
Ininitial roundup of 1.2.0 release items
- Add support for RoCE
- Add support for On Demand Paging
- No longer assume that no driver for a verbs device should be considered
an error condition (usnic devices in particular are moving to libfabric
drivers only, so we will emit a useless warning/error in the presence
of usnic enabled machines)
- Harden some of the argument processing in example programs
- Add support for s390x
- Fix the broken create/destroy flow API
- First release under new management (hence the decision to update to
version 1.2.0 instead of 1.1.9)
In particular, as this release fixes the create/destroy flow API, there
is a need for an updated libmlx4 sources in order to compile against the
fixed API (binary compatibility was maintained, but source compatibility
was not, so you will need the new libmlx4 to compile against the new
libibverbs). Yishai, please post an updated libmlx4 head of repo and
preferably also a source tarball for libmlx4 when it's ready.
Preferably it would include an embedded check for the proper flow API in
your configure scripts.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next reply other threads:[~2015-09-23 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 17:02 Doug Ledford [this message]
[not found] ` <5602DB41.5070700-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-24 14:27 ` libibverbs-1.2.0-rc1 release Yishai Hadas
2015-09-24 15:12 ` Doug Ledford
2015-10-11 9:51 ` Or Gerlitz
[not found] ` <CAJ3xEMjZaG-1oej4nBG4QhEV-TdGtMp0ZiT2m_2A1_ii2wRZpg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-11 14:00 ` Yishai Hadas
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=5602DB41.5070700@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@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;
as well as URLs for NNTP newsgroup(s).