[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5292c0df-74e6-47b3-d51e-8d4b23733a0d@aquantia.com>
Date: Sat, 27 Apr 2019 06:33:39 +0000
From: Igor Russkikh <Igor.Russkikh@...antia.com>
To: Andrew Lunn <andrew@...n.ch>
CC: "David S . Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Nikita Danilov <Nikita.Danilov@...antia.com>,
Dmitry Bogdanov <Dmitry.Bogdanov@...antia.com>
Subject: Re: [PATCH v3 net-next 10/15] net: aquantia: introduce fwreq mutex
On 27.04.2019 0:20, Andrew Lunn wrote:
> On Fri, Apr 26, 2019 at 09:48:02AM +0000, Igor Russkikh wrote:
>> From: Nikita Danilov <ndanilov@...antia.com>
>>
>> Some of FW operations could be invoked simultaneously,
>> from f.e. ethtool context and from service service activity work.
>> Here we introduce a fw mutex to secure and serialize access
>> to FW logic.
>>
>> Signed-off-by: Nikita Danilov <ndanilov@...antia.com>
>> Signed-off-by: Igor Russkikh <igor.russkikh@...antia.com>
>
> I still think it would be a good idea to put in the low level code a
> check that the mutex is actually held when talking to the firmware.
Will do that separately after extra investigation and evaluation.
Igor
Powered by blists - more mailing lists