From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>,
Mike Heinz
<michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>,
"linux-rdma@vger.kernel.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2] IB/util madeye.c
Date: Thu, 27 May 2010 11:10:49 -0700 [thread overview]
Message-ID: <adamxvlw6za.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <CF9C39F99A89134C9CF9C4CCB68B8DDF255F32E4CC-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org> (Sean Hefty's message of "Thu, 27 May 2010 10:42:22 -0700")
> > Do you mean the controls? not the snooping?
> I mean port madeye to calling libibumad. Replace module_params with
> command line options, printk with printf, use the libibumad
> registration calls, etc.
But we would need to extend the user MAD interface to support snooping,
right? How easy would that be to slot in?
Another option would be to rip out all the MAD snooping stuff from the
core and replace it with something based on the kernel's tracing
infrastructure -- that would give us both a low-tech shell-based version
of madeye (based on just using the pretty-printed ASCII dumps from the
kernel trace stuff) and also allow for higher-tech userspace code to do
smarter processing based on the binary trace interface.
- R.
--
Roland Dreier <rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org> || For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
--
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:[~2010-05-27 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 15:51 [PATCH v2] IB/util madeye.c Mike Heinz
[not found] ` <4C2744E8AD2982428C5BFE523DF8CDCB49A488D5D7-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-05-27 16:31 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF255F32E369-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-05-27 16:46 ` Ira Weiny
[not found] ` <20100527094605.790bafee.weiny2-i2BcT+NCU+M@public.gmane.org>
2010-05-27 17:42 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF255F32E4CC-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-05-27 18:10 ` Roland Dreier [this message]
[not found] ` <adamxvlw6za.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-05-27 18:30 ` Hefty, Sean
2010-06-03 16:31 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF255F46352E-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-06-04 16:18 ` Mike Heinz
2010-05-27 21:25 ` Jason Gunthorpe
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=adamxvlw6za.fsf@roland-alpha.cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=weiny2-i2BcT+NCU+M@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