From: Sebastian Riemer <sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: OpenSM 3.3.16 at 100% CPU load, "console off"
Date: Wed, 09 Oct 2013 17:52:47 +0200 [thread overview]
Message-ID: <52557BCF.6030302@profitbricks.com> (raw)
In-Reply-To: <525572FE.5080805-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On 09.10.2013 17:15, Hal Rosenstock wrote:
> What does service restart do in terms of OpenSM ?
>
> Note that the console parameter is _not_ changeable "on the fly" right
> now so if OpenSM is being SIGHUP'd by service restart then this is a
> current limitation (and is clearly not detected/protected against in the
> current code base). It sounds like that may be what is going on.
Yes, it emits SIGHUP. Thanks for the information! The opensm is a
critical component. So IMHO it needs to be fixed in a way that it either
protects itself against such changes by ignoring them on the fly or it
needs to support these changes.
The current situation is not really acceptable and the opensm stability
is crucial. So I'll think about fixing it.
Are you interested in patches in this regard?
Cheers,
Sebastian
--
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-10-09 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 11:10 OpenSM 3.3.16 at 100% CPU load, "console off" Sebastian Riemer
[not found] ` <525539A4.8090700-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-10-09 13:28 ` Hal Rosenstock
[not found] ` <52555A04.8080606-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-10-09 13:30 ` David Dillow
[not found] ` <1381325445.27365.4.camel-a7a0dvSY7KqLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2013-10-09 13:53 ` Sebastian Riemer
2013-10-09 14:00 ` Hal Rosenstock
[not found] ` <52556172.2070707-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-10-09 14:45 ` Sebastian Riemer
[not found] ` <52556BEE.5070409-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-10-09 15:15 ` Hal Rosenstock
[not found] ` <525572FE.5080805-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-10-09 15:52 ` Sebastian Riemer [this message]
[not found] ` <52557BCF.6030302-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-10-09 16:51 ` 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=52557BCF.6030302@profitbricks.com \
--to=sebastian.riemer-eikl63zcoxah+58jc4qpia@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.