netdev - Re: [PATCH net-next v2 00/11] bnxt_en: Implement new driver APIs to send FW messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <163031340881.11172.13384242552118412129.git-patchwork-notify@kernel.org>
Date:   Mon, 30 Aug 2021 08:50:08 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Michael Chan <michael.chan@...adcom.com>
Cc:     davem@...emloft.net, netdev@...r.kernel.org, kuba@...nel.org,
        edwin.peer@...adcom.com, gospo@...adcom.com
Subject: Re: [PATCH net-next v2 00/11] bnxt_en: Implement new driver APIs to send
 FW messages

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Sun, 29 Aug 2021 03:34:55 -0400 you wrote:
> The current driver APIs to send messages to the firmware allow only one
> outstanding message in flight.  There is only one buffer for the firmware
> response for each firmware channel.  To send a firmware message, all
> callers must take a mutex and it is released after the firmware response
> has been read.  This scheme does not allow multiple firmware messages
> in flight.  Firmware may take a long time to respond to some messages
> (e.g. NVRAM related ones) and this causes the mutex to be held for
> a long time, blocking other callers.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,01/11] bnxt_en: remove DMA mapping for KONG response
    https://git.kernel.org/netdev/net-next/c/6c172d59ad79
  - [net-next,v2,02/11] bnxt_en: Refactor the HWRM_VER_GET firmware calls
    https://git.kernel.org/netdev/net-next/c/7b370ad77392
  - [net-next,v2,03/11] bnxt_en: move HWRM API implementation into separate file
    https://git.kernel.org/netdev/net-next/c/3c8c20db769c
  - [net-next,v2,04/11] bnxt_en: introduce new firmware message API based on DMA pools
    https://git.kernel.org/netdev/net-next/c/f9ff578251dc
  - [net-next,v2,05/11] bnxt_en: discard out of sequence HWRM responses
    https://git.kernel.org/netdev/net-next/c/02b9aa106868
  - [net-next,v2,06/11] bnxt_en: add HWRM request assignment API
    https://git.kernel.org/netdev/net-next/c/ecddc29d928d
  - [net-next,v2,07/11] bnxt_en: add support for HWRM request slices
    https://git.kernel.org/netdev/net-next/c/213808170840
  - [net-next,v2,08/11] bnxt_en: use link_lock instead of hwrm_cmd_lock to protect link_info
    https://git.kernel.org/netdev/net-next/c/3c10ed497fa8
  - [net-next,v2,09/11] bnxt_en: update all firmware calls to use the new APIs
    https://git.kernel.org/netdev/net-next/c/bbf33d1d9805
  - [net-next,v2,10/11] bnxt_en: remove legacy HWRM interface
    https://git.kernel.org/netdev/net-next/c/b34695a894b8
  - [net-next,v2,11/11] bnxt_en: support multiple HWRM commands in flight
    https://git.kernel.org/netdev/net-next/c/68f684e257d7

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html