From: David Miller <davem@davemloft.net>
To: roopa@cumulusnetworks.com
Cc: jiri@resnulli.us, steven.lin1@broadcom.com,
netdev@vger.kernel.org, jiri@mellanox.com,
michael.chan@broadcom.com, linux-pci@vger.kernel.org,
linville@tuxdriver.com, gospo@broadcom.com
Subject: Re: [RFC 0/3] Adding config get/set to devlink
Date: Thu, 12 Oct 2017 12:01:13 -0700 (PDT) [thread overview]
Message-ID: <20171012.120113.825151862740889559.davem@davemloft.net> (raw)
In-Reply-To: <CAJieiUiFmBr72yYP9VNtm0VBTNjJcA6Lj5nHJNBjDBC4moxE2A@mail.gmail.com>
From: Roopa Prabhu <roopa@cumulusnetworks.com>
Date: Thu, 12 Oct 2017 07:46:24 -0700
> FWIS, devlink is a driver api just like ethtool is.
Devlink a driver API for doing operations where we don't have a
specific 'netdev' object to work upon.
> and ethtool needs to move to netlink soon...and It would be better to
> not put the rtnl_lock burden on ethtool driver operations. Instead of
> adding yet another driver api, extending devlink seems like a great
> fit to me.
You can use genetlink and avoid RTNL.
Also, Florian Westphal has been pushing the RTNL lock down into the
actual rtnetlink operation implementations. So one does not have to
avoid rtnetlink to avoid the RTNL mutex at all.
next prev parent reply other threads:[~2017-10-12 19:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 13:34 [RFC 0/3] Adding config get/set to devlink Steve Lin
2017-10-12 13:34 ` [RFC 1/3] devlink: Add config parameter get/set operations Steve Lin
2017-10-12 14:03 ` Jiri Pirko
2017-10-12 14:37 ` Steve Lin
2017-10-12 18:12 ` Andy Gospodarek
2017-10-13 7:04 ` Jiri Pirko
2017-10-12 14:15 ` Jiri Pirko
2017-10-12 13:34 ` [RFC 2/3] bnxt: Move generic devlink code to new file Steve Lin
2017-10-12 13:34 ` [RFC 3/3] bnxt: Add devlink support for config get/set Steve Lin
2017-10-12 14:35 ` [RFC 0/3] Adding config get/set to devlink Roopa Prabhu
2017-10-12 14:40 ` Jiri Pirko
2017-10-12 14:46 ` Roopa Prabhu
2017-10-12 15:04 ` Jiri Pirko
2017-10-12 15:31 ` Roopa Prabhu
2017-10-12 15:43 ` Florian Fainelli
2017-10-12 15:43 ` Florian Fainelli
2017-10-12 16:05 ` Roopa Prabhu
2017-10-12 16:05 ` Roopa Prabhu
2017-10-12 19:06 ` David Miller
2017-10-12 19:20 ` Florian Fainelli
2017-10-12 20:12 ` Steve Lin
2017-10-13 7:08 ` Jiri Pirko
2017-10-12 21:36 ` Michal Kubecek
2017-10-12 21:53 ` Roopa Prabhu
2017-10-13 7:11 ` Jiri Pirko
2017-10-14 4:21 ` Roopa Prabhu
2017-10-12 19:01 ` David Miller
2017-10-12 19:01 ` David Miller [this message]
2017-10-12 18:59 ` David Miller
2017-10-12 14:45 ` Steve Lin
2017-10-12 14:51 ` Roopa Prabhu
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=20171012.120113.825151862740889559.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gospo@broadcom.com \
--cc=jiri@mellanox.com \
--cc=jiri@resnulli.us \
--cc=linux-pci@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=steven.lin1@broadcom.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.