* RDMA header inspection
@ 2020-02-03 19:30 Dimitris Dimitropoulos
2020-02-03 20:04 ` Mark Bloch
2020-02-03 20:08 ` Leon Romanovsky
0 siblings, 2 replies; 5+ messages in thread
From: Dimitris Dimitropoulos @ 2020-02-03 19:30 UTC (permalink / raw)
To: linux-rdma
Hi,
I'm trying to inspect RDMA headers and they do not show up on
wireshark. How can I observe RDMA headers ? Also, any header parser
available in the code base that I can link to and use to process the
headers ?
Thank you.
Dimitris
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: RDMA header inspection
2020-02-03 19:30 RDMA header inspection Dimitris Dimitropoulos
@ 2020-02-03 20:04 ` Mark Bloch
2020-02-03 20:08 ` Leon Romanovsky
1 sibling, 0 replies; 5+ messages in thread
From: Mark Bloch @ 2020-02-03 20:04 UTC (permalink / raw)
To: Dimitris Dimitropoulos, linux-rdma
On 2/3/20 11:30 AM, Dimitris Dimitropoulos wrote:
> Hi,
>
> I'm trying to inspect RDMA headers and they do not show up on
> wireshark. How can I observe RDMA headers ? Also, any header parser
> available in the code base that I can link to and use to process the
> headers ?
Usually RDMA packets will not be seen by the end nodes.
What is the link layer IB or RoCE?
If RoCE and you have a switch in the middle, you can probably run wireshark/tcpdump there.
If you are using a driver that implements the right flow steering API you could use libpcap:
https://github.com/the-tcpdump-group/libpcap
The APIs used:
https://github.com/the-tcpdump-group/libpcap/blob/master/pcap-rdmasniff.c
>
>
> Thank you.
>
> Dimitris
>
Mark
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: RDMA header inspection
2020-02-03 19:30 RDMA header inspection Dimitris Dimitropoulos
2020-02-03 20:04 ` Mark Bloch
@ 2020-02-03 20:08 ` Leon Romanovsky
2020-02-04 7:53 ` Parav Pandit
1 sibling, 1 reply; 5+ messages in thread
From: Leon Romanovsky @ 2020-02-03 20:08 UTC (permalink / raw)
To: Dimitris Dimitropoulos; +Cc: linux-rdma
On Mon, Feb 03, 2020 at 11:30:09AM -0800, Dimitris Dimitropoulos wrote:
> Hi,
>
> I'm trying to inspect RDMA headers and they do not show up on
> wireshark. How can I observe RDMA headers ? Also, any header parser
> available in the code base that I can link to and use to process the
> headers ?
The libpcap which is compiled with RDMA support has ability to catch
traffic for mlx4/mlx5 devices.
https://github.com/the-tcpdump-group/libpcap/pull/585
Thanks
>
>
> Thank you.
>
> Dimitris
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: RDMA header inspection
2020-02-03 20:08 ` Leon Romanovsky
@ 2020-02-04 7:53 ` Parav Pandit
2020-03-20 1:09 ` Dimitris Dimitropoulos
0 siblings, 1 reply; 5+ messages in thread
From: Parav Pandit @ 2020-02-04 7:53 UTC (permalink / raw)
To: Leon Romanovsky, Dimitris Dimitropoulos; +Cc: linux-rdma@vger.kernel.org
> From: linux-rdma-owner@vger.kernel.org <linux-rdma-
> owner@vger.kernel.org> On Behalf Of Leon Romanovsky
> Sent: Tuesday, February 4, 2020 1:38 AM
> To: Dimitris Dimitropoulos <d.dimitropoulos@imatrex.com>
> Cc: linux-rdma@vger.kernel.org
> Subject: Re: RDMA header inspection
>
> On Mon, Feb 03, 2020 at 11:30:09AM -0800, Dimitris Dimitropoulos wrote:
> > Hi,
> >
> > I'm trying to inspect RDMA headers and they do not show up on
> > wireshark. How can I observe RDMA headers ? Also, any header parser
> > available in the code base that I can link to and use to process the
> > headers ?
>
> The libpcap which is compiled with RDMA support has ability to catch traffic for
> mlx4/mlx5 devices.
> https://github.com/the-tcpdump-group/libpcap/pull/585
>
If you want to consume this feature in simpler and quicker way, you can follow the steps [1] without affecting your OS userspace environment.
I find it useful and quick way to debug issues.
But feel free ignore my suggestion and use your latest or compiled tcpdump with latest libpcap.
[1] https://hub.docker.com/r/mellanox/tcpdump-rdma
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: RDMA header inspection
2020-02-04 7:53 ` Parav Pandit
@ 2020-03-20 1:09 ` Dimitris Dimitropoulos
0 siblings, 0 replies; 5+ messages in thread
From: Dimitris Dimitropoulos @ 2020-03-20 1:09 UTC (permalink / raw)
To: Parav Pandit; +Cc: Leon Romanovsky, linux-rdma@vger.kernel.org
Hi,
That seems to be the simplest way to view the traffic. I just tried it
successfully on a ConnectX-5 card (Mellanox driver OFED-5.0 on a
Centos 7.7 / Kernel 3.10.0).
Thank you.
Dimitris
On Mon, Feb 3, 2020 at 11:53 PM Parav Pandit <parav@mellanox.com> wrote:
>
>
>
> > From: linux-rdma-owner@vger.kernel.org <linux-rdma-
> > owner@vger.kernel.org> On Behalf Of Leon Romanovsky
> > Sent: Tuesday, February 4, 2020 1:38 AM
> > To: Dimitris Dimitropoulos <d.dimitropoulos@imatrex.com>
> > Cc: linux-rdma@vger.kernel.org
> > Subject: Re: RDMA header inspection
> >
> > On Mon, Feb 03, 2020 at 11:30:09AM -0800, Dimitris Dimitropoulos wrote:
> > > Hi,
> > >
> > > I'm trying to inspect RDMA headers and they do not show up on
> > > wireshark. How can I observe RDMA headers ? Also, any header parser
> > > available in the code base that I can link to and use to process the
> > > headers ?
> >
> > The libpcap which is compiled with RDMA support has ability to catch traffic for
> > mlx4/mlx5 devices.
> > https://github.com/the-tcpdump-group/libpcap/pull/585
> >
>
> If you want to consume this feature in simpler and quicker way, you can follow the steps [1] without affecting your OS userspace environment.
> I find it useful and quick way to debug issues.
>
> But feel free ignore my suggestion and use your latest or compiled tcpdump with latest libpcap.
>
> [1] https://hub.docker.com/r/mellanox/tcpdump-rdma
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-03-20 1:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-02-03 19:30 RDMA header inspection Dimitris Dimitropoulos
2020-02-03 20:04 ` Mark Bloch
2020-02-03 20:08 ` Leon Romanovsky
2020-02-04 7:53 ` Parav Pandit
2020-03-20 1:09 ` Dimitris Dimitropoulos
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).