linux-kernel - finding correct ib_device to call connect()

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>] [day] [month] [year] [list]

Date:	Mon, 29 Dec 2008 01:05:02 -0800 (PST)
From:	Parav Pandit <paravpandit@...oo.com>
To:	Linux kernel <linux-kernel@...r.kernel.org>
Subject: finding correct ib_device to call connect()

Hi,

Is this the right mailing list for Infiniband, RDMA-iWarp related Linux kernel issues?

Assuming yes,
1. Let's say there are two iWarp adapters, they both are in different subnet.
Their respective net_device is configured in different subnet.
(say one from Chelsio and other from Neteffect vendor)

How does connection manager module figures how that a connect() call should be diverted to which ib_device?

Regards,
Parav Pandit

--
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/