From: Andrew Lunn <andrew@lunn.ch>
To: Arkadi Sharshevsky <arkadis@mellanox.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
ivecera@redhat.com, roopa@cumulusnetworks.com,
Florian Fainelli <f.fainelli@gmail.com>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
john.fastabend@gmail.com, Jiri Pirko <jiri@resnulli.us>,
mlxsw <mlxsw@mellanox.com>
Subject: Re: Driver profiles RFC
Date: Tue, 8 Aug 2017 15:54:36 +0200 [thread overview]
Message-ID: <20170808135436.GA2015@lunn.ch> (raw)
In-Reply-To: <6d8560fa-8346-0c43-272d-d39be65ea82f@mellanox.com>
On Tue, Aug 08, 2017 at 04:15:41PM +0300, Arkadi Sharshevsky wrote:
> Drivers may require driver specific information during the init stage.
> For example, memory based shared resource which should be segmented for
> different ASIC processes, such as FDB and LPM lookups.
Hi Arkadi
Have you looked around other subsystems to see if they have already
solved this problem?
How about GPUs? Do they have a similar requirement?
This seems like a generic problem for 'smart' peripherals. How would
you use dpipe with a GPU for example?
Andrew
next prev parent reply other threads:[~2017-08-08 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 13:15 Driver profiles RFC Arkadi Sharshevsky
2017-08-08 13:24 ` Jiri Pirko
2017-08-08 13:54 ` Andrew Lunn [this message]
2017-08-08 15:44 ` Arkadi Sharshevsky
2017-08-08 16:08 ` Roopa Prabhu
2017-08-09 11:43 ` Arkadi Sharshevsky
2017-08-11 14:34 ` Roopa Prabhu
2017-08-11 21:57 ` Jakub Kicinski
2017-08-13 6:32 ` Jiri Pirko
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=20170808135436.GA2015@lunn.ch \
--to=andrew@lunn.ch \
--cc=arkadis@mellanox.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=vivien.didelot@savoirfairelinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).