From: Jesper Dangaard Brouer <brouer@redhat.com>
To: "Rosen, Rami" <rami.rosen@intel.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Jiri Pirko <jiri@resnulli.us>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"idosch@mellanox.com" <idosch@mellanox.com>,
"eladr@mellanox.com" <eladr@mellanox.com>,
"yotamg@mellanox.com" <yotamg@mellanox.com>,
"ogerlitz@mellanox.com" <ogerlitz@mellanox.com>,
"yishaih@mellanox.com" <yishaih@mellanox.com>,
"dledford@redhat.com" <dledford@redhat.com>,
"Hefty, Sean" <sean.hefty@intel.com>,
"hal.rosenstock@gmail.com" <hal.rosenstock@gmail.com>,
"eugenia@mellanox.com" <eugenia@mellanox.com>,
"roopa@cumulusnetworks.com" <roopa@cumulusnetworks.com>,
"nikolay@cumulusnetworks.com" <nikolay@cumulusnetworks.com>,
"hadarh@mellanox.com" <hadarh@mellanox.com>,
"jhs@mojatatu.com" <jhs@mojatatu.com>,
"john.fastabend@gmail.com" <john.fastabend@gmail.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@
Subject: Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it
Date: Fri, 5 Feb 2016 15:29:36 +0100 [thread overview]
Message-ID: <20160205152936.63863d27@redhat.com> (raw)
In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F92CB6D2ED@HASMSX110.ger.corp.intel.com>
On Thu, 4 Feb 2016 19:01:55 +0000
"Rosen, Rami" <rami.rosen@intel.com> wrote:
> Hi,
>
> >Btw, if you add this tool into iproute2 (which would be preferred), >then
> >probably dl should be ok (and easier retrievable in that relation).
>
> +1.
>
> This tool, which uses netlink messages, seems a natural candidate for iproute2.
>
> And also apart from "ip", we have also another short command in
> iproute2, namely "tc", which is yet another justification for using
> the short form with "dl".
I agree that integration into iproute2 is a good idea.
I strongly disagree on introducing such a short command name. Today we
live in a world where you google for usage examples... the ip and tc
commands origin for another time, and IMHO their short names have hurt
them not getting broad usage. Especially it have been difficult to get
people to really adopt "ip", which is also worst search term in the
Internet today...
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2016-02-05 14:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 10:47 [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it Jiri Pirko
2016-02-03 10:47 ` [patch net-next RFC 1/6] Introduce devlink infrastructure Jiri Pirko
2016-02-11 14:31 ` Ivan Vecera
2016-02-11 16:54 ` Jiri Pirko
2016-02-03 10:47 ` [patch net-next RFC 2/6] mlxsw: Implement devlink interface Jiri Pirko
2016-02-03 10:47 ` [patch net-next RFC 3/6] mlxsw: Implement hardware messages notification using devlink Jiri Pirko
2016-02-03 10:48 ` [patch net-next RFC 4/6] mlx4: Implement devlink interface Jiri Pirko
2016-02-16 16:43 ` Or Gerlitz
2016-02-16 16:51 ` Jiri Pirko
2016-02-03 10:48 ` [patch net-next RFC 5/6] mlx4: Implement hardware messages notification using devlink Jiri Pirko
2016-02-03 10:48 ` [patch net-next RFC 6/6] mlx4: Implement port type setting via devlink interface Jiri Pirko
2016-02-03 13:31 ` [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it Jesper Dangaard Brouer
2016-02-03 13:33 ` Jiri Pirko
2016-02-03 15:17 ` Daniel Borkmann
2016-02-04 13:22 ` Hannes Frederic Sowa
2016-02-04 13:26 ` Jiri Pirko
2016-02-05 10:01 ` Hannes Frederic Sowa
2016-02-05 17:38 ` Alexei Starovoitov
2016-02-06 19:40 ` Jiri Pirko
2016-02-08 10:15 ` Hannes Frederic Sowa
2016-02-08 10:55 ` Jiri Pirko
2016-02-08 12:11 ` Hannes Frederic Sowa
2016-02-04 19:01 ` Rosen, Rami
2016-02-05 14:29 ` Jesper Dangaard Brouer [this message]
2016-02-07 20:18 ` roopa
2016-02-08 19:00 ` Doug Ledford
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=20160205152936.63863d27@redhat.com \
--to=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=eladr@mellanox.com \
--cc=eugenia@mellanox.com \
--cc=hadarh@mellanox.com \
--cc=hal.rosenstock@gmail.com \
--cc=idosch@mellanox.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=ogerlitz@mellanox.com \
--cc=rami.rosen@intel.com \
--cc=roopa@cumulusnetworks.com \
--cc=sean.hefty@intel.com \
--cc=yishaih@mellanox.com \
--cc=yotamg@mellanox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.