netdev - Re: [PATCH v2 net-next 0/7] qed*: RDMA and infrastructure for iWARP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170618131443.GA27458@infradead.org>
Date:   Sun, 18 Jun 2017 06:14:43 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Yuval Mintz <Yuval.Mintz@...ium.com>
Cc:     davem@...emloft.net, netdev@...r.kernel.org,
        Michal.Kalderon@...ium.com, linux-rdma@...r.kernel.org
Subject: Re: [PATCH v2 net-next 0/7] qed*: RDMA and infrastructure for iWARP

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?