From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Sebastian Riemer
<sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@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 09:28:36 -0400 [thread overview]
Message-ID: <52555A04.8080606@dev.mellanox.co.il> (raw)
In-Reply-To: <525539A4.8090700-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Hi Sebastian,
On 10/9/2013 7:10 AM, Sebastian Riemer wrote:
> Hi Hal,
>
> we've encountered an issue with OpenSM 3.3.16 and the config option
> "console off".
> OpenSM processes are at 100% CPU load.
>
>>From strace:
> poll([{fd=0, events=POLLIN}], 1, 1000) = 1 ([{fd=0, revents=POLLIN}])
> read(0, "", 4096) = 0
> poll([{fd=0, events=POLLIN}], 1, 1000) = 1 ([{fd=0, revents=POLLIN}])
> read(0, "", 4096) = 0
> poll([{fd=0, events=POLLIN}], 1, 1000) = 1 ([{fd=0, revents=POLLIN}])
> read(0, "", 4096) = 0
So this doesn't block for 1 second and that's why the CPU is 100% ?
> As far as I've seen in the code, the function osm_console() from
> opensm/osm_console.c is the only function which uses poll().
osm_vendor_ibumad has a receiver thread polling umad under the covers of
umad_recv but I think that uses infinite rather than 1 second.
> Is this issue already known or perhaps already fixed?
This area of the console code has not changed in quite a while.
Any idea if this works with older versions of OpenSM ?
This is first I've heard of this issue.
-- Hal
> Thanks,
> 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 13:28 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 [this message]
[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
[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=52555A04.8080606@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@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