From: David Miller <davem@davemloft.net>
To: sudarsana.kalluru@cavium.com
Cc: netdev@vger.kernel.org, Michal.Kalderon@cavium.com
Subject: Re: [PATCH net v2 1/1] bnx2x: Assign unique DMAE channel number for FW DMAE transactions.
Date: Mon, 12 Nov 2018 08:54:55 -0800 (PST) [thread overview]
Message-ID: <20181112.085455.1513459403088791878.davem@davemloft.net> (raw)
In-Reply-To: <20181112022734.22168-1-sudarsana.kalluru@cavium.com>
From: Sudarsana Reddy Kalluru <sudarsana.kalluru@cavium.com>
Date: Sun, 11 Nov 2018 18:27:34 -0800
> Driver assigns DMAE channel 0 for FW as part of START_RAMROD command. FW
> uses this channel for DMAE operations (e.g., TIME_SYNC implementation).
> Driver also uses the same channel 0 for DMAE operations for some of the PFs
> (e.g., PF0 on Port0). This could lead to concurrent access to the DMAE
> channel by FW and driver which is not legal. Hence need to assign unique
> DMAE id for FW.
> Currently following DMAE channels are used by the clients,
> MFW - OCBB/OCSD functionality uses DMAE channel 14/15
> Driver 0-3 and 8-11 (for PF dmae operations)
> 4 and 12 (for stats requests)
> Assigning unique dmae_id '13' to the FW.
>
> Changes from previous version:
> ------------------------------
> v2: Incorporated the review comments.
>
> Signed-off-by: Sudarsana Reddy Kalluru <Sudarsana.Kalluru@cavium.com>
> Signed-off-by: Michal Kalderon <Michal.Kalderon@cavium.com>
Applied.
prev parent reply other threads:[~2018-11-13 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 2:27 [PATCH net v2 1/1] bnx2x: Assign unique DMAE channel number for FW DMAE transactions Sudarsana Reddy Kalluru
2018-11-12 16:54 ` David Miller [this message]
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=20181112.085455.1513459403088791878.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Michal.Kalderon@cavium.com \
--cc=netdev@vger.kernel.org \
--cc=sudarsana.kalluru@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