Roland Dreier wrote:
>> Yep, looks like that's where my cleanup broke things. I rolled this in
>> and pushed it out; I'm testing it myself now.
> My IB port comes to active now, I think that fixed things.
same here, I have IB port coming to active and basic IPoIB, opensm working okay
on the nod
On 10/25/2010 9:44 PM, Joe Perches wrote:
Signed-off-by: Joe Perches
---
drivers/infiniband/hw/amso1100/c2_intr.c |4 ++--
drivers/infiniband/hw/cxgb3/iwch_cm.c|4 ++--
drivers/infiniband/hw/cxgb4/cm.c |4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
Acke
> I have IB port coming to active and basic IPoIB, opensm working okay
> on the node with the current for-next/IBoE bits
doing a little bit stress testing, I came across the below oops, when running
IPoIB
and couple of iperf/udp sessions, it doesn't look like a problem in the IB
stack.
Also wit
> doing a little bit stress testing, I came across the below oops, when running
> IPoIB
> and couple of iperf/udp sessions, it doesn't look like a problem in the IB
> stack.
To trigger this I run from client node the following "iperf -uc 192.168.21.18
-l 64000 -t 72000 -i 1 -b 40g -d -P 4" whe
I'll try to reproduce here. Anyway, I don't see how it could possibly
be related to IBoE.
On Tue, Oct 26, 2010 at 02:19:43PM +0200, Or Gerlitz wrote:
> > I have IB port coming to active and basic IPoIB, opensm working okay
> > on the node with the current for-next/IBoE bits
>
> doing a little bit
The comment some lines above states that disabled devices
must not reset.
Signed-off-by: Nicolas Kaiser
---
drivers/infiniband/hw/ipath/ipath_sysfs.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/infiniband/hw/ipath/ipath_sysfs.c
b/drivers/infiniband/hw/ipath/
Resending. Didn't get any reply after the last posting.
-Original Message-
From: Mike Heinz
Sent: Monday, October 11, 2010 11:34 AM
To: 'linux-rdma@vger.kernel.org'
Subject: [PATCH] Add exponential backoff + random delay to MADs when retrying
after timeout.
This patch builds upon a disc
Resending. Didn't get any reply after sending the last time.
-Original Message-
From: Mike Heinz
Sent: Monday, October 11, 2010 1:24 PM
To: 'linux-rdma@vger.kernel.org'; 'Hefty, Sean'
Cc: Todd Rimmer
Subject: [PATCH] Handling BUSY responses from the SM.
This patch builds upon feedback re
I seemed to already have the amso1100 part, but I picked up the
cxgb3/cxgb4 parts.
- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Linus, please pull from
master.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git for-linus
This tree is also available from kernel.org mirrors at:
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git
for-linus
The big new feature here is support for InfiniBand-o
Hi Linus,
A) I forgot to push out my for-linus branch, so if you tried earlier, it
wasn't there, but it is now:
master.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git for-linus
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git
for-linus
B) It was pointed out
Steve (Wise), any feeling on this (https://patchwork.kernel.org/patch/257761/)?
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
12 matches
Mail list logo
