lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 15 Sep 2020 22:06:45 +0530
From:   sundeep subbaraya <sundeep.lkml@...il.com>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Sunil Kovvuri Goutham <sgoutham@...vell.com>,
        Jiri Pirko <jiri@...nulli.us>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Subbaraya Sundeep Bhatta <sbhatta@...vell.com>
Subject: Re: [EXT] Re: [net-next PATCH 0/2] Introduce mbox tracepoints for Octeontx2

On Tue, Sep 15, 2020 at 9:42 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Tue, 15 Sep 2020 21:22:21 +0530 sundeep subbaraya wrote:
> > > > Make use of the standard devlink tracepoint wherever applicable, and you
> > > > can keep your extra ones if you want (as long as Jiri don't object).
> > >
> > > Sure and noted. I have tried to use devlink tracepoints and since it
> > > could not fit our purpose I used these.
> >
> > Can you please comment.
>
> Comment on what? Restate what I already said? Add the standard
> tracepoint, you can add extra ones where needed.

We did look at using the devlink tracepoint for our purpose and found
it not suitable for our current requirement.
As and when we want to add new tracepoints we will keep this in mind
to see if we can use the devlink one.

So was just checking if Jiri is okay with this.

Powered by blists - more mailing lists