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 11:44:46 -0400 [thread overview]
Message-ID: <5565E66E.90602@dev.mellanox.co.il> (raw)
In-Reply-To: <CAGNdY=4iODDSiYdQ7UQdYBQUi7hs8x8-1BqTQk8ZLmpfeovPeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 5/27/2015 11:31 AM, Jesus Camacho Villanueva wrote:
> The switches are unmanaged.
> Is it possible to ensure in-order packets with managed switches?
No; same issue as I previously mentioned exists with both.
Unmanaged switches just use firmware whereas managed switches have CPU
and kernel in addition to firmware so the system is more complex.
-- Hal
> Jesus
>
> On Wed, May 27, 2015 at 4:30 PM, Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> wrote:
>> On 5/27/2015 10:16 AM, Jesus Camacho Villanueva wrote:
>>> Hi Hal,
>>>
>>> Thanks for your quick response :)
>>>
>>> What you say here makes sense. I have seen this behaviour in one of
>>> the switches, but I don't discard that this problem can arise in other
>>> switches.
>>
>> Note that for MADs, transaction ID is "looser" than traditional
>> transaction ID semantics in that "the combination of TID, SGID, and
>> MgmtClass is different from that of any currently executing operation"
>> and does not imply ordering. If there is ordering required, it is the
>> responsibility of the manager to enforce that.
>>
>>> The switch is: Infiniscale-IV Mellanox Technologies 4xQDR
>>
>> Is it a managed or unmanaged switch ?
>>
>> -- Hal
>
--
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
prev parent reply other threads:[~2015-05-27 15:44 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
[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 [this message]
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=5565E66E.90602@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