From: Or Gerlitz <ogerlitz@mellanox.com>
To: Steve Wise <swise@opengridcomputing.com>,
'Faisal Latif' <faisal.latif@intel.com>
Cc: 'Or Gerlitz' <gerlitz.or@gmail.com>,
'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: Thu, 21 Jan 2016 19:05:48 +0200 [thread overview]
Message-ID: <56A10FEC.5020402@mellanox.com> (raw)
In-Reply-To: <004401d15460$e77fa1b0$b67ee510$@opengridcomputing.com>
On 1/21/2016 5:32 PM, Steve Wise wrote:
> Only a single user-space daemon is used.
Good.
> Someone from Intel might have insight into the architecture and design. Perhaps the intention is that individual drivers might want to have their own handlers for these various operations. But currently they all use the core/common ones.
But if there's single daemon there and one set of pre-defined
callbacks, why different netlink commands are needed? in what case the
damon uses RDMA_NL_NES or RDMA_NL_C4IW or the new define and why?
Or.
WARNING: multiple messages have this Message-ID (diff)
From: Or Gerlitz <ogerlitz@mellanox.com>
To: Steve Wise <swise@opengridcomputing.com>,
'Faisal Latif' <faisal.latif@intel.com>
Cc: 'Or Gerlitz' <gerlitz.or@gmail.com>,
'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: Thu, 21 Jan 2016 19:05:48 +0200 [thread overview]
Message-ID: <56A10FEC.5020402@mellanox.com> (raw)
In-Reply-To: <004401d15460$e77fa1b0$b67ee510$@opengridcomputing.com>
On 1/21/2016 5:32 PM, Steve Wise wrote:
> Only a single user-space daemon is used.
Good.
> Someone from Intel might have insight into the architecture and design. Perhaps the intention is that individual drivers might want to have their own handlers for these various operations. But currently they all use the core/common ones.
But if there's single daemon there and one set of pre-defined
callbacks, why different netlink commands are needed? in what case the
damon uses RDMA_NL_NES or RDMA_NL_C4IW or the new define and why?
Or.
next prev parent reply other threads:[~2016-01-21 17:05 UTC|newest]
Thread overview: 31+ 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
[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
2016-01-20 22:57 ` Steve Wise
2016-01-21 7:53 ` Or Gerlitz
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 15:32 ` Steve Wise
2016-01-21 17:05 ` Or Gerlitz [this message]
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 04/16] i40iw: add connection management code 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=56A10FEC.5020402@mellanox.com \
--to=ogerlitz@mellanox.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 \
--cc=swise@opengridcomputing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.