All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Suresh Shelvapille
	<suri-lFb5ksp6isWhEniVeURVKkEOCMrvLtNR@public.gmane.org>
Cc: 'Ralph Campbell'
	<ralph.campbell-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: How to know if SRQ is being used in SRP?
Date: Thu, 05 Aug 2010 11:16:02 -0700	[thread overview]
Message-ID: <adar5id3oyl.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <D8F95421ED674F1DAC3A9A471854A748-+IkoAhRkys/CbFgIbBqbbjGjJy/sRE9J@public.gmane.org> (Suresh Shelvapille's message of "Thu, 5 Aug 2010 14:05:56 -0400")

 > I am told that the customer has modified the SRP code, which is why I cannot go by the ib_srp.c code. 

Can you not ask the customer??  Or if you have the object code, look for
calls to srq functions in the binary??

  > 1. Would the Syndrome field show CC INVALID if SRQ were being used?
  > If so, in which IB message would it show---RDMA read response, or in
  > an initial RC SEND message or both?

As I said before, the implication is only one way.  If end-to-end flow
control is not used, that does not imply anything -- the CM protocol
allows flow control to be turned off even if an SRQ is not used.

 - R.
-- 
Roland Dreier <rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org> || For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.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

  parent reply	other threads:[~2010-08-05 18:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 14:02 [PATCH v2] IB/srp: use multiple CPU cores more effectively Bart Van Assche
     [not found] ` <201008031602.37294.bvanassche-HInyCGIudOg@public.gmane.org>
2010-08-04 19:45   ` Vladislav Bolkhovitin
     [not found]     ` <4C59C34F.2000400-d+Crzxg7Rs0@public.gmane.org>
2010-08-04 20:40       ` Roland Dreier
     [not found]         ` <adak4o66rir.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-08-05 10:55           ` Bart Van Assche
     [not found]             ` <AANLkTikswdOfqoZOmSqmug4ue3KLv3V8NH9W1ME4tnfQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-05 16:38               ` How to know if SRQ is being used in SRP? Suresh Shelvapille
     [not found]                 ` <8BAAFD34FEF6492A8E3B43698E454B3D-+IkoAhRkys/CbFgIbBqbbjGjJy/sRE9J@public.gmane.org>
2010-08-05 17:42                   ` Ralph Campbell
     [not found]                     ` <1281030129.7414.16.camel-/vjeY7uYZjrPXfVEPVhPGq6RkeBMCJyt@public.gmane.org>
2010-08-05 18:05                       ` Suresh Shelvapille
     [not found]                         ` <D8F95421ED674F1DAC3A9A471854A748-+IkoAhRkys/CbFgIbBqbbjGjJy/sRE9J@public.gmane.org>
2010-08-05 18:16                           ` Roland Dreier [this message]
2010-08-05 18:08                   ` Roland Dreier
2010-08-05 16:58               ` [PATCH v2] IB/srp: use multiple CPU cores more effectively Roland Dreier

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=adar5id3oyl.fsf@roland-alpha.cisco.com \
    --to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ralph.campbell-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org \
    --cc=suri-lFb5ksp6isWhEniVeURVKkEOCMrvLtNR@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.