[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9DD61F30A802C4429A01CA4200E302A7C60C94C3@fmsmsx124.amr.corp.intel.com>
Date: Tue, 18 Feb 2020 20:43:11 +0000
From: "Saleem, Shiraz" <shiraz.saleem@...el.com>
To: Jason Gunthorpe <jgg@...pe.ca>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"Ruhl, Michael J" <michael.j.ruhl@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"nhorman@...hat.com" <nhorman@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>
Subject: RE: [RFC PATCH v4 22/25] RDMA/irdma: Add dynamic tracing for CM
> Subject: Re: [RFC PATCH v4 22/25] RDMA/irdma: Add dynamic tracing for CM
>
> On Wed, Feb 12, 2020 at 11:14:21AM -0800, Jeff Kirsher wrote:
> > From: "Michael J. Ruhl" <michael.j.ruhl@...el.com>
> >
> > Add dynamic tracing functionality to debug connection management
> > issues.
>
> We now have tracing in the core CM, why does a driver need additional tracing?
>
This is specifically for recording driver specific data / paths in connection setup/tear-down flows.
Powered by blists - more mailing lists