From: Hannes Reinecke <hare@suse.de>
To: Shai Malin <smalin@marvell.com>,
netdev@vger.kernel.org, linux-nvme@lists.infradead.org,
davem@davemloft.net, kuba@kernel.org, sagi@grimberg.me,
hch@lst.de, axboe@fb.com, kbusch@kernel.org
Cc: aelior@marvell.com, mkalderon@marvell.com, okulkarni@marvell.com,
pkushwaha@marvell.com, malin1024@gmail.com
Subject: Re: [RFC PATCH v6 13/27] qed: Add NVMeTCP Offload IO Level FW and HW HSI
Date: Fri, 28 May 2021 14:41:43 +0200 [thread overview]
Message-ID: <02fd8ffa-db79-1b19-7faf-e3d2f153c510@suse.de> (raw)
In-Reply-To: <20210527235902.2185-14-smalin@marvell.com>
On 5/28/21 1:58 AM, Shai Malin wrote:
> This patch introduces the NVMeTCP Offload FW and HW HSI in order
> to initialize the IO level configuration into a per IO HW
> resource ("task") as part of the IO path flow.
>
> Acked-by: Igor Russkikh <irusskikh@marvell.com>
> Signed-off-by: Prabhakar Kushwaha <pkushwaha@marvell.com>
> Signed-off-by: Omkar Kulkarni <okulkarni@marvell.com>
> Signed-off-by: Shai Malin <smalin@marvell.com>
> Signed-off-by: Michal Kalderon <mkalderon@marvell.com>
> Signed-off-by: Ariel Elior <aelior@marvell.com>
> ---
> include/linux/qed/nvmetcp_common.h | 335 ++++++++++++++++++++++++++++-
> include/linux/qed/qed_nvmetcp_if.h | 31 +++
> 2 files changed, 365 insertions(+), 1 deletion(-)
> Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, 90409 Nürnberg
GF: F. Imendörffer, HRB 36809 (AG Nürnberg)
next prev parent reply other threads:[~2021-05-28 12:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 23:58 [RFC PATCH v6 00/27] NVMeTCP Offload ULP and QEDN Device Driver Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 01/27] nvme-tcp-offload: Add nvme-tcp-offload - NVMeTCP HW offload ULP Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 02/27] nvme-fabrics: Move NVMF_ALLOWED_OPTS and NVMF_REQUIRED_OPTS definitions Shai Malin
2021-05-28 10:18 ` Hannes Reinecke
2021-05-27 23:58 ` [RFC PATCH v6 03/27] nvme-fabrics: Expose nvmf_check_required_opts() globally Shai Malin
2021-05-28 10:18 ` Hannes Reinecke
2021-05-27 23:58 ` [RFC PATCH v6 04/27] nvme-tcp-offload: Add device scan implementation Shai Malin
2021-05-28 10:28 ` Hannes Reinecke
2021-05-27 23:58 ` [RFC PATCH v6 05/27] nvme-tcp-offload: Add controller level implementation Shai Malin
2021-05-28 11:21 ` Hannes Reinecke
2021-05-31 14:02 ` Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 06/27] nvme-tcp-offload: Add controller level error recovery implementation Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 07/27] nvme-tcp-offload: Add queue level implementation Shai Malin
2021-05-28 11:29 ` Hannes Reinecke
2021-05-31 14:04 ` Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 08/27] nvme-tcp-offload: Add IO " Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 09/27] qed: Add TCP_ULP FW resource layout Shai Malin
2021-05-28 11:31 ` Hannes Reinecke
2021-05-27 23:58 ` [RFC PATCH v6 10/27] qed: Add NVMeTCP Offload PF Level FW and HW HSI Shai Malin
2021-05-28 12:01 ` Hannes Reinecke
2021-05-27 23:58 ` [RFC PATCH v6 11/27] qed: Add NVMeTCP Offload Connection " Shai Malin
2021-05-28 12:41 ` Hannes Reinecke
2021-05-27 23:58 ` [RFC PATCH v6 12/27] qed: Add support of HW filter block Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 13/27] qed: Add NVMeTCP Offload IO Level FW and HW HSI Shai Malin
2021-05-28 12:41 ` Hannes Reinecke [this message]
2021-05-27 23:58 ` [RFC PATCH v6 14/27] qed: Add NVMeTCP Offload IO Level FW Initializations Shai Malin
2021-05-28 12:43 ` Hannes Reinecke
2021-05-27 23:58 ` [RFC PATCH v6 15/27] qed: Add IP services APIs support Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 16/27] qedn: Add qedn - Marvell's NVMeTCP HW offload vendor driver Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 17/27] qedn: Add qedn probe Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 18/27] qedn: Add qedn_claim_dev API support Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 19/27] qedn: Add IRQ and fast-path resources initializations Shai Malin
2021-05-28 12:46 ` Hannes Reinecke
2021-05-27 23:58 ` [RFC PATCH v6 20/27] qedn: Add connection-level slowpath functionality Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 21/27] qedn: Add support of configuring HW filter block Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 22/27] qedn: Add IO level qedn_send_req and fw_cq workqueue Shai Malin
2021-05-28 12:57 ` Hannes Reinecke
2021-05-31 14:12 ` Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 23/27] qedn: Add support of Task and SGL Shai Malin
2021-05-28 13:06 ` Hannes Reinecke
2021-05-31 14:14 ` Shai Malin
2021-05-27 23:58 ` [RFC PATCH v6 24/27] qedn: Add support of NVME ICReq & ICResp Shai Malin
2021-05-28 13:07 ` Hannes Reinecke
2021-05-27 23:59 ` [RFC PATCH v6 25/27] qedn: Add IO level fastpath functionality Shai Malin
2021-05-27 23:59 ` [RFC PATCH v6 26/27] qedn: Add Connection and IO level recovery flows Shai Malin
2021-05-27 23:59 ` [RFC PATCH v6 27/27] qedn: Add support of ASYNC Shai Malin
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=02fd8ffa-db79-1b19-7faf-e3d2f153c510@suse.de \
--to=hare@suse.de \
--cc=aelior@marvell.com \
--cc=axboe@fb.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=malin1024@gmail.com \
--cc=mkalderon@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=okulkarni@marvell.com \
--cc=pkushwaha@marvell.com \
--cc=sagi@grimberg.me \
--cc=smalin@marvell.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).