public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Jesus Camacho Villanueva
	<jesus.camacho-CZJJ9ELfIp3ZJqsBc5GL+g@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: out of order packets when querying all ports in a switch through OpenSM
Date: Wed, 27 May 2015 09:55:04 -0400	[thread overview]
Message-ID: <5565CCB8.8060600@dev.mellanox.co.il> (raw)
In-Reply-To: <CAGNdY=4ox_P_XB+gaFoQvec=j9qp4RKOxrM9vsL_FAXAE3oYow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Jesus,

On 5/27/2015 8:56 AM, Jesus Camacho Villanueva wrote:
> Hello,
> 
> I am trying to send a port info request to all the ports in a switch,
> one after the other.
> 
> I am sending all requests to the same switch in sequence through the
> same directed routing path:
> 
> Request port number 1
> Request port number 2
> Request port number 3
> Request port number 4
> 
> But sometimes I get responses out of order:
> 
> Response port number 2
> Response port number 1
> Response port number 3
> Response port number 4
> 
> Is it possible that the switch is processing port requests out of
> order (or maybe I am doing something wrong)?

One way this could occur is that request to switch for port number 1
either does not make it to switch or response does not make it back and
it times out and is retransmitted by kernel. This depends on how umad is
setup in terms of retries and timeout.

Is it always the same switch or switch type ? What switch is it ?

-- Hal

> Best regards,
> Jesus
> --
> 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

  parent reply	other threads:[~2015-05-27 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 12:56 out of order packets when querying all ports in a switch through OpenSM Jesus Camacho Villanueva
     [not found] ` <CAGNdY=4ox_P_XB+gaFoQvec=j9qp4RKOxrM9vsL_FAXAE3oYow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-27 13:55   ` Hal Rosenstock [this message]
     [not found]     ` <5565CCB8.8060600-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-05-27 14:16       ` Jesus Camacho Villanueva
     [not found]         ` <CAGNdY=6RQS9F4Or+fEudpVj0iRKJ_95LiG0O2+n=GG3WqzKP6w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-27 14:30           ` Hal Rosenstock
     [not found]             ` <5565D518.30602-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-05-27 15:31               ` Jesus Camacho Villanueva
     [not found]                 ` <CAGNdY=4iODDSiYdQ7UQdYBQUi7hs8x8-1BqTQk8ZLmpfeovPeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-27 15:44                   ` Hal Rosenstock

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=5565CCB8.8060600@dev.mellanox.co.il \
    --to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=jesus.camacho-CZJJ9ELfIp3ZJqsBc5GL+g@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