public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Michal Kalderon
	<Michal.Kalderon-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
Cc: ram.amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org,
	yuval.mintz-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org,
	ariel.elior-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org,
	davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [RFC 01/19] qed: Introduce iWARP personality
Date: Tue, 27 Jun 2017 08:36:35 +0300	[thread overview]
Message-ID: <20170627053635.GM1248@mtr-leonro.local> (raw)
In-Reply-To: <1498500429-22557-2-git-send-email-Michal.Kalderon-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>

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

On Mon, Jun 26, 2017 at 09:06:51PM +0300, Michal Kalderon wrote:
> iWARP personality introduced the need for differentiating in several
> places in the code whether we are RoCE, iWARP or either. This
> leads to introducing new macros for querying the personality.
>
> Signed-off-by: Michal Kalderon <Michal.Kalderon-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
> Signed-off-by: Yuval Mintz <Yuval.Mintz-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
> Signed-off-by: Ariel Elior <Ariel.Elior-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
>
> ---
>  drivers/net/ethernet/qlogic/qed/qed.h      | 26 +++++++++++++++++++++++---
>  drivers/net/ethernet/qlogic/qed/qed_cxt.c  |  8 ++++----
>  drivers/net/ethernet/qlogic/qed/qed_dev.c  | 12 +++++-------
>  drivers/net/ethernet/qlogic/qed/qed_l2.c   |  3 +--
>  drivers/net/ethernet/qlogic/qed/qed_ll2.c  |  2 +-
>  drivers/net/ethernet/qlogic/qed/qed_main.c | 17 ++++++++---------
>  include/linux/qed/common_hsi.h             |  2 +-
>  7 files changed, 43 insertions(+), 27 deletions(-)

I see that these changes are in Ethernet part of your driver, but for
RDMA part, there are already available inline functions:
rdma_protocol_iwarp, rdma_protocol_roce.

Please avoid introducing new IS_IWARP/IS_ROCE macros and the decision
should be taken on port level and not on device, despite the fact that
probably your ib_device has only one port.

Thanks

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

  parent reply	other threads:[~2017-06-27  5:36 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
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 [this message]
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=20170627053635.GM1248@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=Michal.Kalderon-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
    --cc=ariel.elior-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ram.amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
    --cc=yuval.mintz-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
    /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