From: "Steve Wise" <swise@opengridcomputing.com>
To: 'Or Gerlitz' <gerlitz.or@gmail.com>,
'Faisal Latif' <faisal.latif@intel.com>
Cc: 'Doug Ledford' <dledford@redhat.com>,
linux-rdma@vger.kernel.org,
'Linux Netdev List' <netdev@vger.kernel.org>,
'Jeff Kirsher' <jeffrey.t.kirsher@intel.com>,
e1000-rdma@lists.sourceforge.net
Subject: RE: [PATCH v3 00/16] add Intel X722 iWARP driver
Date: Wed, 20 Jan 2016 16:57:12 -0600 [thread overview]
Message-ID: <00cf01d153d5$e6248eb0$b26dac10$@opengridcomputing.com> (raw)
In-Reply-To: <CAJ3xEMhxMzAVJUNbBHrG8hia2tcFJ4cuPHpq3t9p0FqPHfYX+Q@mail.gmail.com>
> -----Original Message-----
> From: linux-rdma-owner@vger.kernel.org [mailto:linux-rdma-owner@vger.kernel.org] On Behalf Of Or Gerlitz
> Sent: Wednesday, January 20, 2016 4:25 PM
> To: Faisal Latif
> Cc: Doug Ledford; linux-rdma@vger.kernel.org; Linux Netdev List; Jeff Kirsher; e1000-rdma@lists.sourceforge.net
> Subject: Re: [PATCH v3 00/16] add Intel X722 iWARP driver
>
> On Wed, Jan 20, 2016 at 9:40 PM, Faisal Latif <faisal.latif@intel.com> wrote:
>
> > Changes since v2:
> [...]
> > *move netlink patch up
>
> I also asked you why the port mapper code has to be present in each
> iwarp driver and not part of the IB core stack, and you responded
> "i40iw iwarp driver registers with port mapper and uses its services.
> Beside that it is not the scope of the patch series" -- well, it is
> in the scope of upstream review to pose such questions, please
> address.
>
> Or.
Hey Or,
There is a common service/API in the IB core for iWarp port mapping. See drivers/infinbiand/core/iwpm*.c and include/rdma/iw_portmap.h.
Steve.
next prev parent reply other threads:[~2016-01-20 22:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 19:40 [PATCH v3 00/16] add Intel X722 iWARP driver Faisal Latif
2016-01-20 19:40 ` [PATCH v3 04/16] i40iw: add connection management code Faisal Latif
[not found] ` <1453318816-21672-1-git-send-email-faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-01-20 19:40 ` [PATCH v3 01/16] i40e: Add support for client interface for IWARP driver Faisal Latif
2016-01-20 19:40 ` [PATCH v3 02/16] i40iw: add entry in rdma_netlink Faisal Latif
2016-01-20 19:40 ` [PATCH v3 03/16] i40iw: add main, hdr, status Faisal Latif
2016-01-20 19:40 ` [PATCH v3 05/16] i40iw: add puda code Faisal Latif
2016-01-20 19:40 ` [PATCH v3 07/16] i40iw: add hmc resource files Faisal Latif
2016-01-20 19:40 ` [PATCH v3 08/16] i40iw: add hw and utils files Faisal Latif
2016-01-20 19:40 ` [PATCH v3 11/16] i40iw: add hardware related header files Faisal Latif
2016-01-20 19:40 ` [PATCH v3 13/16] i40iw: user kernel shared files Faisal Latif
2016-01-20 22:24 ` [PATCH v3 00/16] add Intel X722 iWARP driver Or Gerlitz
2016-01-20 22:57 ` Steve Wise [this message]
2016-01-21 7:53 ` Or Gerlitz
[not found] ` <56A08E8F.7090602-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-01-21 15:32 ` Steve Wise
2016-01-21 17:05 ` Or Gerlitz
[not found] ` <56A10FEC.5020402-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-01-21 18:24 ` Faisal Latif
2016-01-21 18:40 ` Or Gerlitz
[not found] ` <CAJ3xEMgE1-EuNBmYVfLoBwjohcxt5tio6wtZn=TYvDAgQgh9cw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-21 19:21 ` David Miller
2016-04-04 7:39 ` Christoph Hellwig
[not found] ` <20160404073929.GA23218-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-04-04 17:59 ` Faisal Latif
2016-01-20 19:40 ` [PATCH v3 06/16] i40iw: add pble resource files Faisal Latif
2016-01-20 19:40 ` [PATCH v3 09/16] i40iw: add files for iwarp interface Faisal Latif
2016-01-20 19:40 ` [PATCH v3 10/16] i40iw: add file to handle cqp calls Faisal Latif
2016-01-20 19:40 ` [PATCH v3 12/16] i40iw: add X722 register file Faisal Latif
2016-01-20 19:40 ` [PATCH v3 14/16] i40iw: virtual channel handling files Faisal Latif
2016-01-20 19:40 ` [PATCH v3 15/16] i40iw: Kconfig and Makefile for iwarp module Faisal Latif
2016-01-20 19:40 ` [PATCH v3 16/16] i40iw: changes for build of i40iw module 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='00cf01d153d5$e6248eb0$b26dac10$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
--cc=dledford@redhat.com \
--cc=e1000-rdma@lists.sourceforge.net \
--cc=faisal.latif@intel.com \
--cc=gerlitz.or@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).