netdev - Re: [PATCH v3 00/16] add Intel X722 iWARP driver

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]

Date:	Thu, 21 Jan 2016 19:05:48 +0200
From:	Or Gerlitz <ogerlitz@...lanox.com>
To:	Steve Wise <swise@...ngridcomputing.com>,
	'Faisal Latif' <faisal.latif@...el.com>
CC:	'Or Gerlitz' <gerlitz.or@...il.com>,
	'Doug Ledford' <dledford@...hat.com>,
	<linux-rdma@...r.kernel.org>,
	'Linux Netdev List' <netdev@...r.kernel.org>,
	'Jeff Kirsher' <jeffrey.t.kirsher@...el.com>,
	<e1000-rdma@...ts.sourceforge.net>
Subject: Re: [PATCH v3 00/16] add Intel X722 iWARP driver

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.