From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Hal Rosenstock <hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org,
Linux RDMA <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: OpenSM: reporting traps 129, 130, 131
Date: Thu, 12 Nov 2009 22:36:04 +0200 [thread overview]
Message-ID: <20091112203604.GS7192@me> (raw)
In-Reply-To: <f0e08f230911120838w2f824a4dnc6b51a68b25bbffd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 11:38 Thu 12 Nov , Hal Rosenstock wrote:
>
> We've cared for several years now (babbling port policy was introduced
> into the master on 7/6/09) but this issue still persists. Are you
> saying no reports for these traps until the trap rate is obeyed ?
If existing trap rate filtering in OpenSM is sufficient we can add
reporting (if somebody needs this). I just don't think that we need to
introduce temporary options.
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:[~2009-11-12 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 14:37 OpenSM: reporting traps 129, 130, 131 Yevgeny Kliteynik
[not found] ` <4AF6D78E.6080600-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2009-11-12 13:46 ` Hal Rosenstock
[not found] ` <f0e08f230911120546q5aa0ed72oc6811cbd2471bc44-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-12 15:42 ` Sasha Khapyorsky
2009-11-12 16:38 ` Hal Rosenstock
[not found] ` <f0e08f230911120838w2f824a4dnc6b51a68b25bbffd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-12 16:39 ` Hal Rosenstock
2009-11-12 20:36 ` Sasha Khapyorsky [this message]
2009-11-13 14:42 ` 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=20091112203604.GS7192@me \
--to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kliteyn-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox