netdev - Re: [RFC iproute2-next] devlink: add info subcommand

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 linux-cve-announce 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 Jan 2019 10:32:38 -0800
From:   Jakub Kicinski <jakub.kicinski@...ronome.com>
To:     Jiri Pirko <jiri@...nulli.us>
Cc:     David Miller <davem@...emloft.net>,
        Linux Netdev List <netdev@...r.kernel.org>,
        OSS Drivers <oss-drivers@...ronome.com>
Subject: Re: [RFC iproute2-next] devlink: add info subcommand

On Tue, 15 Jan 2019 19:05:01 +0100, Jiri Pirko wrote:
> > For versions there may be FW communication required, and reading stuff
> > out of flash.  I bit of overhead for users who just want the list of
> > devlink instances.
> >
> > Having in under dev but as a separate command seems quite nice indeed.
> > Especially given that there can only be a show subcommand..  So:
> >
> > For dump:
> > $ devlink dev info
> >
> > But for get:
> > $ devlink dev pci/0000:82:00.0 info
> >
> > or
> >
> > $ devlink dev info pci/0000:82:00.0
>
> This is aligned with the rest.

Cool, thanks for all the comments!