[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170731.175937.1373949013417491840.davem@davemloft.net>
Date: Mon, 31 Jul 2017 17:59:37 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: simon.horman@...ronome.com
Cc: felix.manlunas@...ium.com, netdev@...r.kernel.org,
raghu.vatsavayi@...ium.com, derek.chickles@...ium.com,
satananda.burla@...ium.com, veerasenareddy.burru@...ium.com,
jakub.kicinski@...ronome.com
Subject: Re: [PATCH V2 net-next 0/2] liquidio: Add support for managing
liquidio adapter
From: Simon Horman <simon.horman@...ronome.com>
Date: Sun, 30 Jul 2017 22:21:04 +0200
> On Fri, Jul 28, 2017 at 11:17:07PM -0700, Felix Manlunas wrote:
>> From: Veerasenareddy Burru <veerasenareddy.burru@...ium.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
Agreed, I've seen no attempt to address this important feedback, which
I agree with.
Powered by blists - more mailing lists