From: Michael Wang <yun.wang-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: "Weiny, Ira" <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Hefty,
Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Moni Shoua <monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] IB/core: Don't warn on no SA support in event handler
Date: Thu, 11 Jun 2015 09:48:27 +0200 [thread overview]
Message-ID: <55793D4B.1010804@profitbricks.com> (raw)
In-Reply-To: <2807E5FD2F6FDA4886F6618EAC48510E11099957-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 06/10/2015 06:15 PM, Weiny, Ira wrote:
>>>> Registering an event handler is done for a device. This device may
>>>> have one RoCE port (no SA cap) and one InfiniBand port (has SA cap).
>>>> Therefore, warning from the event handler about a specific port that
>>>> doesn't have SA cap is correct but pollutes the kernel log without a
>>>> need.
>>>
>>> Maybe we should think about register event handler per port :-P
>>
>> I agree, though I think that can be added separately from this change.
>
> Also agreed. We identified many places where we should split support to be per port while we did this work. We need to start working up to that. For the time being we should not break existing users (or in this case annoy them... ;-)
IMHO we can do some reform inside ib_dispatch_event(), where we already have
the port number related to the event, if we could have an event_handler_list
per port and classified the callback inside ib_register_event_handler(), then
we can call the handler on the right port meanwhile won't annoy the user ;-)
Regards,
Michael Wang
>
> Ira
>
--
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:[~2015-06-11 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 9:13 [PATCH] IB/core: Don't warn on no SA support in event handler Moni Shoua
[not found] ` <1433927612-20517-1-git-send-email-monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-06-10 10:12 ` Michael Wang
[not found] ` <55780D8C.1070600-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2015-06-10 15:28 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373A8FE66CA-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-06-10 16:15 ` Weiny, Ira
[not found] ` <2807E5FD2F6FDA4886F6618EAC48510E11099957-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-06-11 7:48 ` Michael Wang [this message]
2015-06-11 5:03 ` Doug Ledford
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=55793D4B.1010804@profitbricks.com \
--to=yun.wang-eikl63zcoxah+58jc4qpia@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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