Hi,
OFED 1.5.2-rc2 is available
Notes:
The tarball is available on:
http://www.openfabrics.org/downloads/OFED/ofed-1.5.2/OFED-1.5.2-rc2.tgz
To get BUILD_ID run ofed_info
Please report any issues in bugzilla https://bugs.openfabrics.org/ for
OFED 1.5.2
Vladimir Tziporet
VLANs are part of L2 in Ethernet -- when you resolve a destination L3 address
to an L2 address, you get the outgoing interface, which also determines the
VLAN.
I think this approach has an advantage over an RDMA device per VLAN in that you
keep the standard OS VLAN management (vconfig).
I
On Fri, Jun 25, 2010 at 11:04:28AM +0300, Liran Liss wrote:
VLANs are part of L2 in Ethernet -- when you resolve a destination
L3 address to an L2 address, you get the outgoing interface, which
also determines the VLAN. I think this approach has an advantage
over an RDMA device per VLAN in
On the other hand trying to hook offloaded iWARP into the normal
stack
does seem to lead to a mess. I see DaveM's point: TCP port space is
just the beginning -- filtering, queueing, etc also have config that
ultimately an offload device would want to hook too.
TCP port space
(BTW, Sean, did AF_IB's sockaddr include a scoping field, and did you
figure out some way to make that work?)
The af_ib does include a scoping field, but the last set of patches doesn't
make use of it.
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a
To my understanding, our discussion touches two topics. One is
to solve the TCP port space issue, the other is more general, its about
proper integration of offloaded TCP within Linux. So, the second
topic is a generalization of the first.
Regarding the first topic, what I was about to
