linux-kernel - Re: InfiniBand/RDMA merge plans for 2.6.33

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: <4B2875F8.4080107@voltaire.com>
Date:	Wed, 16 Dec 2009 07:54:00 +0200
From:	Or Gerlitz <ogerlitz@...taire.com>
To:	Eli Cohen <eli@....mellanox.co.il>
CC:	Roland Dreier <rdreier@...co.com>, linux-kernel@...r.kernel.org,
	linux-rdma@...r.kernel.org
Subject: Re: InfiniBand/RDMA merge plans for 2.6.33

Eli Cohen wrote:
>>  - IBoE.  In principle I think this is starting to get there.  Still
>>    want to see better ABI compatibility at least, and also make sure
>>    the interface chosen works for both rdmacm and non-rdmacm applications.
>>     
>> Based on this, I am going to send a new patch set, a few days after 2.6.33-rc1 is out
Eli, here are some more issues which should be on the table and you 
might want to look at before posting a new version of the patches (or 
else if you want to handle them down the road of the review process 
that's fine)

- loopback support , Liran commented that this works, does this mean 
only firmware fix is needed?

- below-the-cover-addr-resolve-in-create-AH flow races e.g 
https://bugs.openfabrics.org/show_bug.cgi?id=1866

- L2 Ethernet integration for rdma-cm based apps, namely at minimum have 
the <src/dst (unicast) mac, vlan ID, vlan Priority, mtu> gang to comply 
with packets sent by the network stack for the same IP route.

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