From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Linux RDMA list <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC 0/2] IB/umad: Export mad snooping to userspace
Date: Tue, 12 Oct 2010 14:35:28 -0600 [thread overview]
Message-ID: <20101012203528.GP24268@obsidianresearch.com> (raw)
In-Reply-To: <CF9C39F99A89134C9CF9C4CCB68B8DDF25B7DAA11D-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Tue, Oct 12, 2010 at 12:10:37PM -0700, Hefty, Sean wrote:
> The kernel mad interface allows a client to view all
> sent and received MADs. This has proven to be a useful
> debugging technique when paired with the external kernel
> module, madeye. However, madeye was never intended to
> be submitted upstream.
>
> A couple of alternatives have been proposed for making
> this functionality available in the upstream kernel,
> using trace events or exporting the snooping interface
> to user space. This patch series takes the latter approach.
TBH, I think this would be much better off integrating with the
existing paths tcpdump/setc uses rather than yet again something new
and unique. I think everone who has to actually use the IB stuff in
real life would be estatic if wireshark just worked...
Yes, I realize that is a bit awkward.. But maybe it is time we had a
netdev for the raw IB device?
Jason
--
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-10-12 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 19:10 [RFC 0/2] IB/umad: Export mad snooping to userspace Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25B7DAA11D-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-10-12 20:35 ` Jason Gunthorpe [this message]
[not found] ` <20101012203528.GP24268-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-12 20:54 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25B7DAA2A6-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-10-12 21:10 ` Jason Gunthorpe
[not found] ` <20101012211052.GT24268-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-12 22:50 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25B7DAA46E-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-10-12 23:22 ` Opensm crash with OFED 1.5 Suresh Shelvapille
[not found] ` <091262BDA0A846A0B62CB3BEDB366DBC-+IkoAhRkys/CbFgIbBqbbjGjJy/sRE9J@public.gmane.org>
2010-10-13 19:06 ` Suresh Shelvapille
[not found] ` <EC5B6AE4937B444290B7D4D10BC489A5-+IkoAhRkys/CbFgIbBqbbjGjJy/sRE9J@public.gmane.org>
2010-10-19 22:17 ` Suresh Shelvapille
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=20101012203528.GP24268@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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