From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Albert Chu <chu11-i2BcT+NCU+M@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] opensm/osm_console.c: Support portstatus output for incorrect link speeds
Date: Fri, 22 Feb 2013 14:33:56 -0500 [thread overview]
Message-ID: <5127C824.2090108@dev.mellanox.co.il> (raw)
In-Reply-To: <1361489963.24405.68.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
Hi Al,
On 2/21/2013 6:39 PM, Albert Chu wrote:
> Usually coinciding with use of the force_link_speed configuration option,
> some link speeds can be observed to be incorrect. For example, a link
> may be active at QDR even if SDR & DDR speeds are the only ones enabled.
Are you referring to the fact that after setting the enabled speed, the
IB spec does not mandate a link renegotiation and hence one may not have
occurred so the enabled speed can be out of whack with the active speed ?
Also, isn't there a similar issue with extended speeds (and
force_link_speed_ext) ? If so, should that also be part of this patch ?
Same issue also is there for link width as it works the same way as link
speed. Maybe that too is yet another patch.
What do you think ?
-- Hal
> Under these scenarios, the portstatus may incorrectly output port status,
> confusing users.
>
> A new port output status of "incorrect speed" differentiates ports in this
> state from other states, so as to not confuse users.
>
> Signed-off-by: Albert Chu <chu11-i2BcT+NCU+M@public.gmane.org>
<snip...>
--
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:[~2013-02-22 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 23:39 [PATCH] opensm/osm_console.c: Support portstatus output for incorrect link speeds Albert Chu
[not found] ` <1361489963.24405.68.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2013-02-22 19:33 ` Hal Rosenstock [this message]
[not found] ` <5127C824.2090108-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-02-22 23:20 ` Albert Chu
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=5127C824.2090108@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=chu11-i2BcT+NCU+M@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