From: Simon Horman <simon.horman@netronome.com>
To: Felix Manlunas <felix.manlunas@cavium.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
raghu.vatsavayi@cavium.com, derek.chickles@cavium.com,
satananda.burla@cavium.com, veerasenareddy.burru@cavium.com,
Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: Re: [PATCH V2 net-next 0/2] liquidio: Add support for managing liquidio adapter
Date: Sun, 30 Jul 2017 22:21:04 +0200 [thread overview]
Message-ID: <20170730202103.GA8969@vergenet.net> (raw)
In-Reply-To: <20170729061707.GA1134@felix-thinkpad.cavium.com>
On Fri, Jul 28, 2017 at 11:17:07PM -0700, Felix Manlunas wrote:
> From: Veerasenareddy Burru <veerasenareddy.burru@cavium.com>
>
> The LiquidIO adapter has processor cores that can run Linux. This patch
> set adds support to create a virtual Ethernet interface on host to
> communicate with applications running on Linux in the LiquidIO adapter.
> The virtual Ethernet interface also provides login access to Linux on
> LiquidIO through ssh for management and debugging.
As per the somewhat more detailed feedback provided by my colleague Jakub
Kicinski to v1 of this patchset[1] I am concerned that this patchset breaks down
the long standing practice of not granting direct access to firmware from
userspace.
[1] https://www.spinics.net/lists/netdev/msg444929.html
next prev parent reply other threads:[~2017-07-30 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 6:17 [PATCH V2 net-next 0/2] liquidio: Add support for managing liquidio adapter Felix Manlunas
2017-07-29 6:18 ` [PATCH V2 net-next 1/2] liquidio: Add support to pass meta information to firmware Felix Manlunas
2017-07-29 6:18 ` [PATCH V2 net-next 2/2] liquidio: Add support to create management interface Felix Manlunas
2017-07-30 20:21 ` Simon Horman [this message]
2017-08-01 0:59 ` [PATCH V2 net-next 0/2] liquidio: Add support for managing liquidio adapter David Miller
2017-08-01 2:09 ` Felix Manlunas
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=20170730202103.GA8969@vergenet.net \
--to=simon.horman@netronome.com \
--cc=davem@davemloft.net \
--cc=derek.chickles@cavium.com \
--cc=felix.manlunas@cavium.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=raghu.vatsavayi@cavium.com \
--cc=satananda.burla@cavium.com \
--cc=veerasenareddy.burru@cavium.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).