From: Ralph Campbell <ralph.campbell-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
To: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
Cc: Linux-RDMA <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Work completions generated after a queue pair has made the transition to an error state
Date: Tue, 12 Oct 2010 11:50:35 -0700 [thread overview]
Message-ID: <1286909435.27343.93.camel@chromite.mv.qlogic.com> (raw)
In-Reply-To: <AANLkTimcxsymqmzoki=quCH+a2sq_fPb4YOmf3gqrzqh-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
I haven't seen it. It isn't supposed to happen.
What hardware and software are you using and how do you
reproduce it?
On Tue, 2010-10-12 at 11:38 -0700, Bart Van Assche wrote:
> Hello,
>
> Has anyone already tried to process the work completions generated by
> a HCA after the state of a queue pair has been changed to IB_QPS_ERR ?
> With the hardware/firmware/driver combination I have tested I have
> observed the following:
> * Multiple completions with the same wr_id and nonzero (error) status
> were received by the application, while all work requests queued with
> the flag IB_SEND_SIGNALED had a unique wr_id.
> * Completions with non-zero (error) status and a wr_id / opcode
> combination were received that were never queued by the application.
> Note: some work requests were queued with and some without the flag
> IB_SEND_SIGNALED. I'm not sure however whether that has anything to do
> with the observed behavior.
>
> This behavior is easy to reproduce. If I interpret the InfiniBand
> Architecture Specification correctly, this behavior is non-compliant.
>
> Has anyone been looking into this before ?
>
> Bart.
> --
> 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
>
--
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 prev parent reply other threads:[~2010-10-12 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 18:38 Work completions generated after a queue pair has made the transition to an error state Bart Van Assche
[not found] ` <AANLkTimcxsymqmzoki=quCH+a2sq_fPb4YOmf3gqrzqh-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-12 18:50 ` Ralph Campbell [this message]
[not found] ` <1286909435.27343.93.camel-/vjeY7uYZjrPXfVEPVhPGq6RkeBMCJyt@public.gmane.org>
2010-10-12 18:58 ` Bart Van Assche
[not found] ` <AANLkTi=72Y+coH1Ke4U-Xk7Eaqpw5pipWRqXEQr7dOau-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-12 20:22 ` Eli Cohen
2010-10-13 12:37 ` Eli Cohen
2010-10-13 13:51 ` Or Gerlitz
[not found] ` <4CB5B94E.4080802-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2010-10-13 14:23 ` Eli Cohen
2010-10-13 16:05 ` Roland Dreier
[not found] ` <adawrpmyt5w.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2010-10-13 16:32 ` Eli Cohen
2010-10-13 16:18 ` Roland Dreier
[not found] ` <adapqveyskb.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2010-10-13 16:55 ` Bart Van Assche
2010-10-12 18:52 ` Or Gerlitz
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=1286909435.27343.93.camel@chromite.mv.qlogic.com \
--to=ralph.campbell-h88zbnxc6kdqt0dzr+alfa@public.gmane.org \
--cc=bvanassche-HInyCGIudOg@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