From: "Michael J. Ruhl" <michael.j.ruhl-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v2 0/4] ibacm: acmp retry issues
Date: Mon, 13 Nov 2017 16:23:50 -0500 [thread overview]
Message-ID: <20171113212220.24293.97479.stgit@phlsvslse11.ph.intel.com> (raw)
While testing the retry mechanism for the acmp provider, I observed
that the retry event_wait() did not appear to be working correctly.
After studying the issue a bit more, I discovered that there were a
couple of issues.
This patch set addresses those issues.
v2 - added patch for MONOTONIC time base
---
Michael J. Ruhl (4):
ibacm: Fix an incorrect expiration check for the retry timer
ibacm: Calculate correct tv_nsec value in event_wait()
ibacm: Fix a retry loop calculation race condition
ibacm: Use MONOTONIC time base to avoid timer expiration issues
ibacm/linux/osd.h | 25 ++++++++++++++++---------
ibacm/prov/acmp/src/acmp.c | 12 +++++++-----
2 files changed, 23 insertions(+), 14 deletions(-)
--
--
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
next reply other threads:[~2017-11-13 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 21:23 Michael J. Ruhl [this message]
[not found] ` <20171113212220.24293.97479.stgit-K+u1se/DcYrLESAwzcoQNrvm/XP+8Wra@public.gmane.org>
2017-11-13 21:24 ` [PATCH v2 1/4] ibacm: Fix an incorrect expiration check for the retry timer Michael J. Ruhl
2017-11-13 21:24 ` [PATCH v2 2/4] ibacm: Calculate correct tv_nsec value in event_wait() Michael J. Ruhl
2017-11-13 21:24 ` [PATCH v2 3/4] ibacm: Fix a retry loop calculation race condition Michael J. Ruhl
2017-11-13 21:25 ` [PATCH v2 4/4] ibacm: Use MONOTONIC time base to avoid timer expiration issues Michael J. Ruhl
[not found] ` <20171113212454.24293.68783.stgit-K+u1se/DcYrLESAwzcoQNrvm/XP+8Wra@public.gmane.org>
2017-11-14 3:04 ` Jason Gunthorpe
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=20171113212220.24293.97479.stgit@phlsvslse11.ph.intel.com \
--to=michael.j.ruhl-ral2jqcrhueavxtiumwx3w@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