From: Sasha Khapyorsky <sashakvolt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] opensm: update internal PortInfo state for any ports
Date: Mon, 22 Jul 2013 18:40:34 +0300 [thread overview]
Message-ID: <20130722154032.GA23909@gmail.com> (raw)
In-Reply-To: <51E006B5.3060808-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Hi Hal,
On 09:37 Fri 12 Jul , Hal Rosenstock wrote:
>
> What difference does it make ? Does this patch fix some operational
> issue ? Is there any harm in not keeping the complete PortInfo when port
> is DOWN ?
AFAIK it doesn't harm in the current state. However, I'm prepering the
patches, which will let to OpenSM work on stand alone port. For such
mode this fix is critical.
Will recent with other patches shortly.
Sasha
--
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-07-22 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 20:56 [PATCH] opensm: update internal PortInfo state for any ports Sasha Khapyorsky
[not found] ` <20130707205219.GA6084-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-07-12 13:37 ` Hal Rosenstock
[not found] ` <51E006B5.3060808-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-07-22 15:40 ` Sasha Khapyorsky [this message]
[not found] ` <20130722154032.GA23909-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-08-08 15:03 ` 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=20130722154032.GA23909@gmail.com \
--to=sashakvolt-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@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 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.