[PATCH] opensm: Clean up event subscriptions if a port goes away

2013-09-05 Thread Line Holen
Event subscriptions needs to be cleaned up if a port goes away. If the port comes online again later it may no longer want to receive the events on the same QPN. If the old QPN is used for something else the SM forwarding events may cause QKey violations. Signed-off-by: Line Holen

Re: [PATCH][MINOR] osm_sa_informinfo.c Add attribute info to log messages

2013-09-05 Thread Hal Rosenstock
On 9/3/2013 7:31 AM, Line Holen wrote: Signed-off-by: Line Holen line.ho...@oracle.com Thanks. Applied with minor change noted below. --- diff --git a/opensm/osm_sa_informinfo.c b/opensm/osm_sa_informinfo.c index f32b88b..bf1fe97 100644 --- a/opensm/osm_sa_informinfo.c +++

Re: [PATCH] osm_sa_guidinfo_record.c False duplicate GUID error messages

2013-09-05 Thread Hal Rosenstock
On 9/3/2013 7:30 AM, Line Holen wrote: If the same request is received twice then the second one will cause error messages indicating duplicate alias GUIDs. In this case this is a false warning. The second request should be treated as a void and return success to the requester.

[PATCH opensm] osm_sa_guidinfo_record.c: False duplicate GUID error messages

2013-09-05 Thread Hal Rosenstock
If the same request is received twice then the second one will cause error messages indicating duplicate alias GUIDs. In this case this is a false warning. The second request should be treated as a void and return success to the requester. Signed-off-by: Line Holen line.ho...@oracle.com

Re: rtnl_lock deadlock on 3.10

2013-09-05 Thread Steve Wise
On 9/5/2013 5:02 AM, Bart Van Assche wrote: On 07/30/13 14:54, Steve Wise wrote: On 7/29/2013 6:02 PM, Shawn Bohrer wrote: On Mon, Jul 15, 2013 at 09:38:19AM -0500, Shawn Bohrer wrote: On Wed, Jul 03, 2013 at 08:26:11PM +0300, Or Gerlitz wrote: On 03/07/2013 20:22, Shawn Bohrer wrote: On

Re: rtnl_lock deadlock on 3.10

2013-09-05 Thread Shawn Bohrer
On Thu, Sep 05, 2013 at 10:14:51AM -0500, Steve Wise wrote: On 9/5/2013 5:02 AM, Bart Van Assche wrote: On 07/30/13 14:54, Steve Wise wrote: On 7/29/2013 6:02 PM, Shawn Bohrer wrote: On Mon, Jul 15, 2013 at 09:38:19AM -0500, Shawn Bohrer wrote: On Wed, Jul 03, 2013 at 08:26:11PM +0300, Or

RE: [PATCH 0/4] RDMA/nes and RDMA/cxgb4: iWARP Port Mapper Overview

2013-09-05 Thread Nikolova, Tatyana E
Hello Steve, Thank you for the feedback. I think there are lots of #defines and enums replicated in both nes_netlink.h and c4iw_netlink.h. For example, the IWPM_* defines and enums. It seems like we could put all this in a common header file to be included by all iwarp providers?

Re: Strange NFS client ACK behaviour

2013-09-05 Thread Wendy Cheng
CC linux-nfs .. maybe this is obvious to someone there ... Two comments inlined below. On Tue, Sep 3, 2013 at 11:28 AM, Markus Stockhausen stockhau...@collogia.de wrote: Hello, we observed a performance drop in our IPoIB NFS backup infrastructure since we switched to machines with newer

RE: [PATCH 0/4] RDMA/nes and RDMA/cxgb4: iWARP Port Mapper Overview

2013-09-05 Thread Nikolova, Tatyana E
Hello Or, Does this series follows the netconf 2011session e.g from this link http://vger.kernel.org/netconf2011_slides/pj_netconf2011.ppt? Yes Thanks, Tatyana -Original Message- From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-ow...@vger.kernel.org] On Behalf Of Or Gerlitz

Re: [PATCH opensm] osm_sa_guidinfo_record.c: False duplicate GUID error messages

2013-09-05 Thread Line Holen
Looks good to me. Thanks, Line On 09/05/13 16:18, Hal Rosenstock wrote: If the same request is received twice then the second one will cause error messages indicating duplicate alias GUIDs. In this case this is a false warning. The second request should be treated as a void and return success

RE: [PATCH 0/4] RDMA/nes and RDMA/cxgb4: iWARP Port Mapper Overview

2013-09-05 Thread Nikolova, Tatyana E
Hello Sean, + RDMA_NL_NES, + RDMA_NL_C4IW Why is the communication with the daemon device specific? These enums are necessary. The communication with the IWPM daemon is device specific, because each device is a different netlink client and needs to register with netlink a set