RE: CQ overrun with ib_send_bw

2010-08-17 Thread Tziporet Koren
On 8/13/2010 10:21 PM, Ralph Campbell wrote: On Fri, 2010-08-13 at 12:14 -0700, Hefty, Sean wrote: I know there is a bug with ib_send_bw -b (bi-directional) since it doesn't create a CQ that is large enough for all the posted sends *and* receives. I have tried several times to get the

RE: CQ overrun with ib_send_bw

2010-08-17 Thread Amir Ancel
Hi Sean, We've seen this issue as well. Can you send the patch directly to us ? Added Raz from my team which replaces Ido while he is OOO. Thanks, Amir Ancel Performance Team Manager Mellanox Technologies -Original Message- From: Tziporet Koren Sent: Tuesday, August 17, 2010 2:19

Re: [PATCHv9 09/12] ib_core: Add VLAN support to IBoE

2010-08-17 Thread Eli Cohen
On Mon, Aug 16, 2010 at 03:17:42PM -0700, Roland Dreier wrote: I'm having a hard time figuring out what this sentence has to do with this patch. I don't see anywhere in the patch where the sl field is used except for copying the TOS into it, and I don't see what user priority field might be

Re: [PATCHv9 09/12] ib_core: Add VLAN support to IBoE

2010-08-17 Thread Roland Dreier
I'm having a hard time figuring out what this sentence has to do with this patch. I don't see anywhere in the patch where the sl field is used except for copying the TOS into it, and I don't see what user priority field might be referring to. (per the RoCE spec) the 3 LSbs of the

Re: [PATCH v1 09/10] mlx4_fc: Implement fcoe/fcoib offload driver, fcoib initialization protocol driver

2010-08-17 Thread Joe Eykholt
On 8/16/10 3:16 PM, Vu Pham wrote: 0009-mlx4_fc-Implement-fcoe-fcoib-offload-driver-fcoib-in.patch From 0b10d95be067595dbb050d3cc2c779372038aec4 Mon Sep 17 00:00:00 2001 From: Vu Pham v...@vu-lt.mti.mtl.com Date: Mon, 16 Aug 2010 14:47:34 -0700 Subject: [PATCH 09/10] mlx4_fc:

Re: [PATCHv9 09/12] ib_core: Add VLAN support to IBoE

2010-08-17 Thread Eli Cohen
On Tue, Aug 17, 2010 at 7:43 PM, Roland Dreier rdre...@cisco.com wrote: OK but as I said I don't see what that has to do with this patch. We thought it was appropriate to put this info here. Maybe we should move it to PATCH0? With current API at least the consumer only specifies the SGID

RE: CQ overrun with ib_send_bw

2010-08-17 Thread Ralph Campbell
The patch is attached. On Tue, 2010-08-17 at 04:36 -0700, Amir Ancel wrote: Hi Sean, We've seen this issue as well. Can you send the patch directly to us ? Added Raz from my team which replaces Ido while he is OOO. Thanks, Amir Ancel Performance Team Manager Mellanox

RE: CQ overrun with ib_send_bw

2010-08-17 Thread Amir Ancel
Thanks, We'll apply it soon. Amir Ancel Performance Team Manager Mellanox Technologies -Original Message- From: Ralph Campbell [mailto:ralph.campb...@qlogic.com] Sent: Tuesday, August 17, 2010 9:59 PM To: Amir Ancel Cc: Tziporet Koren; Hefty, Sean; Ido Shamay; Sumeet Lahorani;

[PATCH v5 0/1] IB/ipoib: fix dangling pointer references to ipoib_neigh and ipoib_path

2010-08-17 Thread Ralph Campbell
Hopefully, this is the last update needed to this patch and it can be applied. It has been in use within QLogic for several months without problems. Changes from v4 to v5: Removed the break; in ipoib_cm_flush_path() so now the function comment matches the code. Updated the error case code in

[PATCH v5] IB/ipoib: fix dangling pointer references to ipoib_neigh and ipoib_path

2010-08-17 Thread Ralph Campbell
Basically, a struct sk_buff has a pointer to a struct dst_entry which has a pointer to a struct neighbour. IPoIB uses struct neighbour.ha to store the IB hardware address and a pointer to a struct ipoib_neigh. When using connected mode, struct ipoib_neigh has a pointer to struct ipoib_cm_tx which

Re: [PATCH v5 0/1] IB/ipoib: fix dangling pointer references to ipoib_neigh and ipoib_path

2010-08-17 Thread Ralph Campbell
BTW, I will be around today and tomorrow to reply to comments but then I will be on vacation through August. -- 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