Paul
Solaris has its own stack implementation of the IB components. We do
run some basic interoperability test's on various components (I can confirm
about IPoIB) between solaris and OpenIB stack.
Thanks
Nitin
Paul Baxter wrote:
Can anybody comment on recent experience regarding
Michael Krause wrote:
At 01:01 PM 11/11/2005, Nitin Hande wrote:
Michael Krause wrote:
At 10:28 AM 11/9/2005, Rick Frank wrote:
Yes, the application is responsible for detecting lost msgs at the
application level - the transport can not do this.
RDS does not guarantee that a message has
Michael Krause wrote:
At 10:28 AM 11/9/2005, Rick Frank wrote:
Yes, the application is responsible for detecting lost msgs at the
application level - the transport can not do this.
RDS does not guarantee that a message has been delivered to the
application - just that once the transport has
failed for ff12:401b:8001:0:0:0::, status
-22
b0.8001: multicast join failed for ff12:401b:8001:0:0:0::,
status -22
Thanks
Nitin
-Forwarded Message-
From: Hal Rosenstock [EMAIL PROTECTED]
To: Nitin Hande [EMAIL PROTECTED]
Cc: openib openib-general@openib.org
Hal,
[comments below]
On Wed, 2005-02-23 at 02:19, Hal Rosenstock wrote:
On Tue, 2005-02-22 at 22:56, Nitin Hande wrote:
So I tried the latest patches and preliminarily things seem to be
working fine.
Yipee.
[snip..]
So after this test above, I try to run snoop on the solaris
Hal,
On Thu, 2005-02-17 at 13:12, Hal Rosenstock wrote:
Hi Nitin,
On Wed, 2005-02-16 at 17:33, Nitin Hande wrote:
On Wed, 2005-02-16 at 13:26, Hal Rosenstock wrote:
On Wed, 2005-02-16 at 16:08, Nitin Hande wrote:
Hal,
[snip..]
[snip...]
Before the patch
On Wed, 2005-02-16 at 13:26, Hal Rosenstock wrote:
On Wed, 2005-02-16 at 16:08, Nitin Hande wrote:
Hal,
[snip..]
Here is the trace of 256 sized MTU:
Outgoing MAD:
BaseVersion: 0x1
MgmtClass: 0x3 - SubnAdm
ClassVersion: 0x2
R_Method: 0x12
I have a hunch for whats happening here, but before I jump into any
conclusions, I am seeing some other issue between Solaris IPoIB driver
and OpenSM. After joining the Broadcast group, the PathRecord Response
coming from OpenSM signals an error with Invalid GUID. I wonder why,
Here is the mad
On Tue, 2005-02-15 at 15:57, Hal Rosenstock wrote:
On Tue, 2005-02-15 at 17:45, Nitin Hande wrote:
Here is the osm log, I think we may have a lead, the dest GID is wrong:
:
Feb 15 23:29:57 [43005960] - osm_sm_mcgrp_join: Port 0x0002c901097651d1
joining MLID 0xC001.
Feb 15 23:29:57
Tom Duffy wrote:
On Fri, 2005-02-11 at 20:11 -0500, Hal Rosenstock wrote:
The log indicates that the MTU is 4 which is 2048. I also saw this in
the IB trace.
Ok, I will ask some other Solaris IB guys as well...
Yes, I would like the patch.
BTW, Solaris does work now (Yippie),
Tom Duffy wrote:
On Fri, 2005-02-11 at 20:21 -0800, Nitin Hande wrote:
Allright, so I am not seeing this anymore on the test setup here. I will
keep a watch and conduct some more experiments over weekend if time permits.
Does that mean you fixed it? Or can't reproduce it? Can you ping
Nitin Hande wrote:
Hal/Roland,
Hal Rosenstock wrote:
On Tue, 2004-11-09 at 12:07, Roland Dreier wrote:
multiport bonding/failover
(although my feeling is that it would be better to extend the existing
bonding driver rather than trying to put this in the IPoIB driver),
I'm not clear
Roland Dreier wrote:
Tom Would you really bring both interfaces up? If this is a
Tom problem, the spec should have the pkey be part of the link
Tom local address.
It actually seems to work fine to bring up multiple IPv6 interfaces
that end up with the same link local address
signed off by: Nitin Hande [EMAIL PROTECTED]
I would appreciate if someone can review my patch to enable inet6
address on ib interface. This is the first cut, will like to hear from
all. I plan to setup a bugzilla account and append this patch to the bug
that Tom has created for inet6.
diff
All,
Thanks for your comments,
Roland Dreier wrote:
Nitin I would appreciate if someone can review my patch to enable
Nitin inet6 address on ib interface. This is the first cut, will
Nitin like to hear from all. I plan to setup a bugzilla account
Nitin and append this patch
Roland Dreier wrote:
By the way, can anyone explain the following to me (an IPv6 rookie):
# ping6 -I ib0 fe80::202:c901:78c:e461
PING fe80::202:c901:78c:e461(fe80::202:c901:78c:e461) from
fe80::202:c901:7fc:c711 ib0: 56 data bytes
64 bytes from fe80::202:c901:78c:e461:
Roland Dreier wrote:
By the way, can anyone explain the following to me (an IPv6 rookie):
# ping6 -I ib0 fe80::202:c901:78c:e461
PING fe80::202:c901:78c:e461(fe80::202:c901:78c:e461) from
fe80::202:c901:7fc:c711 ib0: 56 data bytes
64 bytes from fe80::202:c901:78c:e461:
Hal Rosenstock wrote:
On Wed, 2004-11-10 at 00:55, Roland Dreier wrote:
It seems that MAD handling is still not quite right. It seems in my
set up that IPoIB is not seeing the response to its MCMember
set... (it does look like the query is reaching the SM)
This is a separate issue from
Tom Duffy wrote:
On Tue, 2004-11-09 at 15:23 -0800, [EMAIL PROTECTED] wrote:
Author: halr
Date: 2004-11-09 15:23:07 -0800 (Tue, 09 Nov 2004)
New Revision: 1186
Modified:
gen2/trunk/src/linux-kernel/infiniband/core/agent.c
Log:
Fix agent_mad_send PCI mapping and gather address and length
Roland Dreier wrote:
Nitin certainly it does break my x86_64 setup too. Can we revert
Nitin back to working set of bits please ?
It's actually not an architecture issue -- it's an issue if your node
is more than one hop from the SM. You should be able to use the patch
I just posted
20 matches
Mail list logo
