[EMAIL PROTECTED] wrote on Tue, 22 Aug 2006 09:23 -0500:
something like the attached patch? does not incude the ib and gm changes..
Looks good to me (the cleanups too :)). Can you copy the tcp
implementation into ib and gm too, just the free()? Then we won't
have a broken tree until somebody
Pete Wyckoff wrote:
[EMAIL PROTECTED] wrote on Tue, 22 Aug 2006 09:23 -0500:
something like the attached patch? does not incude the ib and gm changes..
Looks good to me (the cleanups too :)). Can you copy the tcp
implementation into ib and gm too, just the free()? Then we won't
have a
On Aug 22, 2006, at 11:22 AM, Pete Wyckoff wrote:
[EMAIL PROTECTED] wrote on Tue, 22 Aug 2006 09:52 -0400:
What is the purpose of the Request To Send (RTS) and Clear To Send
(CTS) messages in the IB and other BMI implementations? Is it to
check if resources are available on the receiver (i.e.
[EMAIL PROTECTED] wrote on Mon, 21 Aug 2006 13:34 -0500:
FYI I was finally cleared to upgrade my cluster to RHEL4 (2.6 kernel).
Unfortunately this doesn't look like it fixed my problem. Doing any
operations on a pvfs2 filesystem over native infiniband (i.e. not tcp or
IPoIB) are extermely
[EMAIL PROTECTED] wrote on Tue, 22 Aug 2006 14:21 -0400:
Ok. MX does this underneath the covers for me. If my send is small
(32 KB by default), it buffers the data and the send can complete
immediately. Larger sends are held on the sender until a matching
receive is posted. If the
On Aug 22, 2006, at 3:34 PM, Pete Wyckoff wrote:
[EMAIL PROTECTED] wrote on Tue, 22 Aug 2006 14:21 -0400:
Ok. MX does this underneath the covers for me. If my send is small
(32 KB by default), it buffers the data and the send can complete
immediately. Larger sends are held on the sender until
[EMAIL PROTECTED] wrote on Tue, 22 Aug 2006 16:18 -0400:
MX provides 64 bits of match info for sends/recvs. I plan to
partition the bits as follows:
bits comment
0-3 msg_type (conn_req, conn_ack, expected, unexpected, ...?)
4-7 reserved for credits (if used)
8-15 reserved
15-31
