netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Faisal Latif <faisal.latif@intel.com>
To: Or Gerlitz <ogerlitz@mellanox.com>
Cc: "dledford@redhat.com" <dledford@redhat.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	"e1000-rdma@lists.sourceforge.net"
	<e1000-rdma@lists.sourceforge.net>
Subject: Re: [PATCH V1 15/16] i40iw: add entry in rdma_netlink
Date: Thu, 24 Dec 2015 01:05:51 -0600	[thread overview]
Message-ID: <20151224070551.GA13684@flatif-MOBL1> (raw)
In-Reply-To: <567AD0C7.3010309@mellanox.com>

On Wed, Dec 23, 2015 at 08:50:15AM -0800, Or Gerlitz wrote:
> On 12/22/2015 1:13 AM, Faisal Latif wrote:
> > Add entry for port mapper services.
> >
> > Signed-off-by: Faisal Latif <faisal.latif@intel.com>
> > ---
> >   include/uapi/rdma/rdma_netlink.h | 1 +
> >   1 file changed, 1 insertion(+)
> >
> > diff --git a/include/uapi/rdma/rdma_netlink.h b/include/uapi/rdma/rdma_netlink.h
> > index c19a5dc..4fa418d 100644
> > --- a/include/uapi/rdma/rdma_netlink.h
> > +++ b/include/uapi/rdma/rdma_netlink.h
> > @@ -8,6 +8,7 @@ enum {
> >   	RDMA_NL_NES,
> >   	RDMA_NL_C4IW,
> >   	RDMA_NL_LS,	/* RDMA Local Services */
> > +	RDMA_NL_I40IW,
> >   	RDMA_NL_NUM_CLIENTS
> >   };
> >   
> Do you use this value in down-stream patches of the series? if yes, 
> change the order to have this and other IB core changes before the code 
> that use that.

Yes, I will move this patch up before it being used.

> 
> Why the iwarp port mapper implementationhas to be repeated in each 
> driver? can you join your code in a common place and avoid the duplication?
> 
> root@r-dcs58 hw]# git grep RDMA_NL_ nes
> nes/nes.c:      [RDMA_NL_IWPM_REG_PID] = {.dump = iwpm_register_pid_cb},
> nes/nes.c:      [RDMA_NL_IWPM_ADD_MAPPING] = {.dump = iwpm_add_mapping_cb},
> nes/nes.c:      [RDMA_NL_IWPM_QUERY_MAPPING] = {.dump = 
> iwpm_add_and_query_mapping_cb},
> nes/nes.c:      [RDMA_NL_IWPM_REMOTE_INFO] = {.dump = iwpm_remote_info_cb},
> nes/nes.c:      [RDMA_NL_IWPM_HANDLE_ERR] = {.dump = iwpm_mapping_error_cb},
> nes/nes.c:      [RDMA_NL_IWPM_MAPINFO] = {.dump = iwpm_mapping_info_cb},
> nes/nes.c:      [RDMA_NL_IWPM_MAPINFO_NUM] = {.dump = 
> iwpm_ack_mapping_info_cb}
> nes/nes.c:      if (ibnl_add_client(RDMA_NL_NES, RDMA_NL_IWPM_NUM_OPS, 
> nes_nl_cb_table))
> nes/nes.c:      ret = iwpm_init(RDMA_NL_NES);
> nes/nes.c:      ibnl_remove_client(RDMA_NL_NES);
> nes/nes.c:      ibnl_remove_client(RDMA_NL_NES);
> nes/nes.c:      iwpm_exit(RDMA_NL_NES);
> nes/nes_cm.c: &mapped_sockaddr, RDMA_NL_NES);
> nes/nes_cm.c:   return iwpm_remove_mapping(&local_sockaddr, RDMA_NL_NES);
> nes/nes_cm.c:                           &remote_addr, RDMA_NL_NES);
> nes/nes_cm.c:           iwpm_err = iwpm_register_pid(&pm_reg_msg, 
> RDMA_NL_NES);
> nes/nes_cm.c:                   iwpm_err = iwpm_add_mapping(&pm_msg, 
> RDMA_NL_NES);
> nes/nes_cm.c:   iwpm_err = iwpm_register_pid(&pm_reg_msg, RDMA_NL_NES);
> nes/nes_cm.c:           iwpm_err = iwpm_add_and_query_mapping(&pm_msg, 
> RDMA_NL_NES);
> 
> [root@r-dcs58 hw]# git grep RDMA_NL_ cxgb4/
> 
> cxgb4/cm.c: iwpm_remove_mapping(&ep->com.local_addr, RDMA_NL_C4IW);
> cxgb4/cm.c: &child_ep->com.remote_addr, RDMA_NL_C4IW);
> cxgb4/cm.c:     iwpm_err = iwpm_register_pid(&pm_reg_msg, RDMA_NL_C4IW);
> cxgb4/cm.c:             iwpm_err = iwpm_add_and_query_mapping(&pm_msg, 
> RDMA_NL_C4IW);
> cxgb4/cm.c: &ep->com.mapped_local_addr, RDMA_NL_C4IW)) {
> cxgb4/cm.c: iwpm_remove_mapping(&ep->com.local_addr, RDMA_NL_C4IW);
> cxgb4/cm.c:     iwpm_err = iwpm_register_pid(&pm_reg_msg, RDMA_NL_C4IW);
> cxgb4/cm.c:             iwpm_err = iwpm_add_mapping(&pm_msg, RDMA_NL_C4IW);
> cxgb4/cm.c: &ep->com.mapped_local_addr, RDMA_NL_C4IW)) {
> cxgb4/device.c: [RDMA_NL_IWPM_REG_PID] = {.dump = iwpm_register_pid_cb},
> cxgb4/device.c: [RDMA_NL_IWPM_ADD_MAPPING] = {.dump = iwpm_add_mapping_cb},
> cxgb4/device.c: [RDMA_NL_IWPM_QUERY_MAPPING] = {.dump = 
> iwpm_add_and_query_mapping_cb},
> cxgb4/device.c: [RDMA_NL_IWPM_HANDLE_ERR] = {.dump = iwpm_mapping_error_cb},
> cxgb4/device.c: [RDMA_NL_IWPM_REMOTE_INFO] = {.dump = iwpm_remote_info_cb},
> cxgb4/device.c: [RDMA_NL_IWPM_MAPINFO] = {.dump = iwpm_mapping_info_cb},
> cxgb4/device.c: [RDMA_NL_IWPM_MAPINFO_NUM] = {.dump = 
> iwpm_ack_mapping_info_cb}
> cxgb4/device.c: if (ibnl_add_client(RDMA_NL_C4IW, RDMA_NL_IWPM_NUM_OPS,
> cxgb4/device.c: err = iwpm_init(RDMA_NL_C4IW);
> cxgb4/device.c:         ibnl_remove_client(RDMA_NL_C4IW);
> cxgb4/device.c: iwpm_exit(RDMA_NL_C4IW);
> cxgb4/device.c: ibnl_remove_client(RDMA_NL_C4IW);
> 

i40iw iwarp driver registers with port mapper and uses its services. Beside that it is not
the scope of the patch series.

Thanks
Faisal

  reply	other threads:[~2015-12-24  7:05 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 23:13 [PATCH V1 00/16] add Intel(R) X722 iWARP driver Faisal Latif
     [not found] ` <1450739596-23276-1-git-send-email-faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-12-21 23:13   ` [PATCH V1 01/16] i40e: Add support for client interface for IWARP driver Faisal Latif
2015-12-21 23:13     ` [PATCH V1 02/16] i40iw: add main, hdr, status Faisal Latif
     [not found]       ` <1450739596-23276-3-git-send-email-faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-12-21 23:13         ` [PATCH V1 03/16] i40iw: add connection management code Faisal Latif
     [not found]           ` <1450739596-23276-4-git-send-email-faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-12-21 23:13             ` [PATCH V1 04/16] i40iw: add puda code Faisal Latif
2015-12-21 23:13               ` [PATCH V1 05/16] i40iw: add pble resource files Faisal Latif
2015-12-21 23:13                 ` [PATCH V1 06/16] i40iw: add hmc " Faisal Latif
2015-12-21 23:13                   ` [PATCH V1 07/16] i40iw: add hw and utils files Faisal Latif
2015-12-21 23:13                     ` [PATCH V1 08/16] i40iw: add files for iwarp interface Faisal Latif
2015-12-21 23:13                       ` [PATCH V1 09/16] i40iw: add file to handle cqp calls Faisal Latif
2015-12-21 23:13                         ` [PATCH V1 10/16] i40iw: add hardware related header files Faisal Latif
     [not found]                           ` <1450739596-23276-11-git-send-email-faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-12-21 23:13                             ` [PATCH V1 11/16] i40iw: add X722 register file Faisal Latif
     [not found]                               ` <1450739596-23276-12-git-send-email-faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-12-21 23:13                                 ` [PATCH V1 12/16] i40iw: user kernel shared files Faisal Latif
     [not found]                                   ` <1450739596-23276-13-git-send-email-faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-12-21 23:13                                     ` [PATCH V1 13/16] i40iw: virtual channel handling files Faisal Latif
     [not found]                                       ` <1450739596-23276-14-git-send-email-faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-12-21 23:13                                         ` [PATCH V1 14/16] i40iw: Kconfig and Kbuild for iwarp module Faisal Latif
     [not found]                                           ` <1450739596-23276-15-git-send-email-faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-12-21 23:13                                             ` [PATCH V1 15/16] i40iw: add entry in rdma_netlink Faisal Latif
2015-12-21 23:13                                               ` [PATCH V1 16/16] i40iw: changes for build of i40iw module Faisal Latif
2015-12-22  0:40                                                 ` kbuild test robot
     [not found]                                               ` <1450739596-23276-16-git-send-email-faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-12-23 16:50                                                 ` [PATCH V1 15/16] i40iw: add entry in rdma_netlink Or Gerlitz
2015-12-24  7:05                                                   ` Faisal Latif [this message]
2015-12-24  8:24                                                     ` Or Gerlitz
     [not found]                       ` <1450739596-23276-9-git-send-email-faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-12-23 16:42                         ` [PATCH V1 08/16] i40iw: add files for iwarp interface Or Gerlitz
2015-12-24  7:31                           ` Faisal Latif
2015-12-24  8:25                             ` Or Gerlitz
2015-12-24 19:36                               ` Faisal Latif
2015-12-22 19:09   ` [PATCH V1 00/16] add Intel(R) X722 iWARP driver Doug Ledford
2015-12-23 16:09   ` Doug Ledford
     [not found]     ` <567AC754.5020508-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-12-23 16:35       ` Faisal Latif
2015-12-23 16:39         ` Or Gerlitz
     [not found]           ` <567ACE44.20608-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-12-24  7:09             ` Faisal Latif
2015-12-23 17:24         ` Doug Ledford
2015-12-23 17:05   ` Or Gerlitz
     [not found]     ` <567AD444.10204-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-12-24  7:25       ` Faisal Latif

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=20151224070551.GA13684@flatif-MOBL1 \
    --to=faisal.latif@intel.com \
    --cc=dledford@redhat.com \
    --cc=e1000-rdma@lists.sourceforge.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.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).