From: Christoph Hellwig <hch@infradead.org>
To: Yuval Mintz <Yuval.Mintz@cavium.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Michal.Kalderon@cavium.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/7] qed*: RDMA and infrastructure for iWARP
Date: Sun, 18 Jun 2017 06:14:43 -0700 [thread overview]
Message-ID: <20170618131443.GA27458@infradead.org> (raw)
In-Reply-To: <20170618115035.2156-1-Yuval.Mintz@cavium.com>
On Sun, Jun 18, 2017 at 02:50:28PM +0300, Yuval Mintz wrote:
> This series focuses on RDMA in general with emphasis on required changes
> toward adding iWARP support. The vast majority of the changes introduced
> are in qed/qede, with a couple of small changes to qedr
> [mentioned below].
Btw, can you explain us how you are going to expose RoCE vs iWarp?
Is it going to be a per-port setting? Are you going to use different
ib_device structures or do you plan to differenciate at another level?
next prev parent reply other threads:[~2017-06-18 13:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 11:50 [PATCH v2 net-next 0/7] qed*: RDMA and infrastructure for iWARP Yuval Mintz
[not found] ` <20170618115035.2156-1-Yuval.Mintz-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
2017-06-18 11:50 ` [PATCH v2 net-next 1/7] qed: Chain support for external PBL Yuval Mintz
2017-06-18 11:50 ` [PATCH v2 net-next 3/7] qed: Disable RoCE dpm when DCBx change occurs Yuval Mintz
2017-06-18 11:50 ` [PATCH v2 net-next 4/7] qed*: Rename qede_roce.[ch] Yuval Mintz
[not found] ` <20170618115035.2156-5-Yuval.Mintz-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
2017-06-18 12:00 ` Kalderon, Michal
2017-06-18 11:50 ` [PATCH v2 net-next 6/7] qed: Wait for resources before FUNC_CLOSE Yuval Mintz
2017-06-18 16:29 ` [PATCH v2 net-next 0/7] qed*: RDMA and infrastructure for iWARP David Miller
2017-06-18 17:54 ` Mintz, Yuval
2017-06-19 1:40 ` David Miller
[not found] ` <BLUPR0701MB20047CD16002072436A61EA38DC70-v5ruerSQ/oj1oiTf6dR/AE5OhdzP3rhOnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-06-19 2:36 ` Andrew Lunn
2017-06-18 11:50 ` [PATCH v2 net-next 2/7] qed: RoCE EDPM to honor PFC Yuval Mintz
2017-06-18 11:50 ` [PATCH v2 net-next 5/7] qed*: Set rdma generic functions prefix Yuval Mintz
2017-06-18 11:50 ` [PATCH v2 net-next 7/7] qed: SPQ async callback registration Yuval Mintz
2017-06-18 13:14 ` Christoph Hellwig [this message]
2017-06-19 6:28 ` [PATCH v2 net-next 0/7] qed*: RDMA and infrastructure for iWARP 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=20170618131443.GA27458@infradead.org \
--to=hch@infradead.org \
--cc=Michal.Kalderon@cavium.com \
--cc=Yuval.Mintz@cavium.com \
--cc=davem@davemloft.net \
--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).