public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Michal Kalderon <Michal.Kalderon@cavium.com>
Cc: ram.amrani@cavium.com, yuval.mintz@cavium.com,
	ariel.elior@cavium.com, davem@davemloft.net,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	dledford@redhat.com
Subject: Re: [RFC 02/19] qed: Implement iWARP initialization, teardown and qp operations
Date: Tue, 27 Jun 2017 08:45:41 +0300	[thread overview]
Message-ID: <20170627054541.GN1248@mtr-leonro.local> (raw)
In-Reply-To: <1498500429-22557-3-git-send-email-Michal.Kalderon@cavium.com>

[-- Attachment #1: Type: text/plain, Size: 646 bytes --]

On Mon, Jun 26, 2017 at 09:06:52PM +0300, Michal Kalderon wrote:
> This patch adds iWARP support for flows that have common code
> between RoCE and iWARP, such as initialization, teardown and
> qp setup verbs: create, destroy, modify, query.
> It introduces the iWARP specific files qed_iwarp.[ch] and
> iwarp_common.h
>
> Signed-off-by: Michal Kalderon <Michal.Kalderon@cavium.com>
> Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com>
> Signed-off-by: Ariel Elior <Ariel.Elior@cavium.com>
>
> ---

<...>

> +#define QED_IWARP_PARAM_P2P		(1)

<...>

> +
> +	iwarp_info->peer2peer = QED_IWARP_PARAM_P2P;

Can you shed a light what is it?

Thanks

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-06-27  5:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 18:06 [RFC 00/19] qed*: Add iWARP support for QL4xxxx Michal Kalderon
2017-06-26 18:06 ` [RFC 02/19] qed: Implement iWARP initialization, teardown and qp operations Michal Kalderon
2017-06-27  5:45   ` Leon Romanovsky [this message]
2017-06-27  8:33     ` Kalderon, Michal
2017-06-26 18:06 ` [RFC 03/19] qed: Rename some ll2 related defines Michal Kalderon
     [not found] ` <1498500429-22557-1-git-send-email-Michal.Kalderon-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
2017-06-26 18:06   ` [RFC 01/19] qed: Introduce iWARP personality Michal Kalderon
     [not found]     ` <1498500429-22557-2-git-send-email-Michal.Kalderon-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
2017-06-27  5:36       ` Leon Romanovsky
2017-06-27  8:17         ` Kalderon, Michal
2017-06-26 18:06   ` [RFC 04/19] qed: Add iWARP support in ll2 connections Michal Kalderon
2017-06-26 18:06   ` [RFC 05/19] qed: iWARP CM - setup a ll2 connection for handling SYN packets Michal Kalderon
2017-06-26 18:06   ` [RFC 06/19] qed: iWARP CM add listener functions and initial SYN processing Michal Kalderon
2017-06-26 18:06   ` [RFC 07/19] qed: iWARP CM add passive side connect Michal Kalderon
2017-06-26 18:07   ` [RFC 12/19] qed: Add iWARP support for physical queue allocation Michal Kalderon
2017-06-26 18:07   ` [RFC 16/19] RDMA/qedr: Add support for read with invalidate, supported in iWARP Michal Kalderon
2017-06-26 18:07   ` [RFC 17/19] RDMA/qedr: Add iWARP connection management qp related callbacks Michal Kalderon
2017-06-26 18:07   ` [RFC 18/19] RDMA/qedr: Add iWARP connection management functions Michal Kalderon
2017-06-26 18:07   ` [RFC 19/19] qed*: Add iWARP enablement support Michal Kalderon
2017-06-26 18:06 ` [RFC 08/19] qed: iWARP CM add active side connect Michal Kalderon
2017-06-26 18:06 ` [RFC 09/19] qed: iWARP implement disconnect flows Michal Kalderon
2017-06-26 18:07 ` [RFC 10/19] qed: iWARP CM add error handling Michal Kalderon
2017-06-26 18:07 ` [RFC 11/19] qed: Add iWARP protocol support in context allocation Michal Kalderon
2017-06-26 18:07 ` [RFC 13/19] RDMA/qedr: Rename the qedr_cm file as a preparation for iWARP support Michal Kalderon
2017-06-26 18:07 ` [RFC 14/19] RDMA/qedr: Add support for registering an iWARP device Michal Kalderon
2017-06-26 18:07 ` [RFC 15/19] RDMA/qedr: Add iWARP support in existing verbs Michal Kalderon
2017-06-27  5:27   ` Leon Romanovsky
2017-06-27  8:18     ` Kalderon, Michal

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=20170627054541.GN1248@mtr-leonro.local \
    --to=leon@kernel.org \
    --cc=Michal.Kalderon@cavium.com \
    --cc=ariel.elior@cavium.com \
    --cc=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ram.amrani@cavium.com \
    --cc=yuval.mintz@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