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] [day] [month] [year] [list]
Message-ID: <B21373C3-87EB-4D13-95B2-7D5FC39AEEEB@cisco.com>
Date:	Tue, 28 Apr 2015 20:17:02 +0000
From:	"Dave Goodell (dgoodell)" <dgoodell@...co.com>
To:	"Hefty, Sean" <sean.hefty@...el.com>
CC:	Tom Talpey <tom@...pey.com>, Doug Ledford <dledford@...hat.com>,
	"Weiny, Ira" <ira.weiny@...el.com>,
	Michael Wang <yun.wang@...fitbricks.com>,
	"Liran Liss" <liranl@...lanox.com>,
	Roland Dreier <roland@...nel.org>,
	Hal Rosenstock <hal@....mellanox.co.il>,
	"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Steve Wise <swise@...ngridcomputing.com>,
	Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
	Tom Tucker <tom@...ngridcomputing.com>,
	Hoang-Nam Nguyen <hnguyen@...ibm.com>,
	"raisch@...ibm.com" <raisch@...ibm.com>,
	infinipath <infinipath@...el.com>, Eli Cohen <eli@...lanox.com>,
	"Latif, Faisal" <faisal.latif@...el.com>,
	"Jack Morgenstein" <jackm@....mellanox.co.il>,
	Or Gerlitz <ogerlitz@...lanox.com>,
	Haggai Eran <haggaie@...lanox.com>
Subject: Re: [PATCH v6 01/26] IB/Verbs: Implement new callback
 query_transport()

On Apr 28, 2015, at 2:53 PM, Hefty, Sean <sean.hefty@...el.com> wrote:

>> Is the concern here about CM issues or the UDP ports used by the actual
>> usNIC RQs? 
> 
> UDP port space sharing

For the UDP port used by the usNIC QP, the usnic_verbs kernel driver requires user space to pass a file descriptor of a regular UDP socket down at create_qp time.  The reference count on this socket is incremented to make sure that the socket can't disappear out from under us.  Then an RX filter is installed in the NIC which matches UDP/IP/Ethernet packets that are destined for the UDP port to which the given socket is already bound.  So there is a real UDP socket to make most of the usual things happen in the net stack, but the raw UDP/IP/Ethernet packets get delivered directly to the user space queues by the NIC.  E.g., "netstat" and "lsof" show you proper addressing information, though obviously any information related to data-path statistics will not be accurate.  At teardown we just reverse the steps.

However, I'm not sure if that's the sort of information you were looking for.

-Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ