Signed-off-by: Line Holen
---
diff --git a/opensm/osm_db_files.c b/opensm/osm_db_files.c
index 513cf85..9219722 100644
--- a/opensm/osm_db_files.c
+++ b/opensm/osm_db_files.c
@@ -2,6 +2,7 @@
* Copyright (c) 2004-2009 Voltaire, Inc. All rights reserved.
* Copyright (c) 2002-2007 Mellanox Tech
2013/9/10 Andreas Bluemle :
> Since I have added these workarounds to my version of the librdmacm
> library, I can at least start up ceph using LD_PRELOAD and end up in
> a healthy ceph cluster state.
Have you seen any performance improvement by using LD_PRELOAD with ceph?
Which throughput are you
On 12/09/2013 08:26, Devesh Sharma wrote:
I don't see any patches to librdmacm/libibverbs git to call _EX version of
uverbs commands.
We've posted the kernel patches, that should be enough for the review.
If you have any specific questions re user
space aspects of this series, feel free to s
Inline Below:
On Thu, Sep 12, 2013 at 4:15 PM, Or Gerlitz wrote:
> On 12/09/2013 08:26, Devesh Sharma wrote:
>>
>> I don't see any patches to librdmacm/libibverbs git to call _EX version of
>> uverbs commands.
>
>
> We've posted the kernel patches, that should be enough for the review. If
> you h
Inline Below on Second question:
On Thu, Sep 12, 2013 at 4:15 PM, Or Gerlitz wrote:
> On 12/09/2013 08:26, Devesh Sharma wrote:
>>
>> I don't see any patches to librdmacm/libibverbs git to call _EX version of
>> uverbs commands.
>
>
> We've posted the kernel patches, that should be enough for the
On Thu, 12 Sep 2013 12:20:03 +0200
Gandalf Corvotempesta wrote:
> 2013/9/10 Andreas Bluemle :
> > Since I have added these workarounds to my version of the librdmacm
> > library, I can at least start up ceph using LD_PRELOAD and end up in
> > a healthy ceph cluster state.
>
> Have you seen any p
On 12/09/2013 14:31, Devesh Sharma wrote:
On Thu, Sep 12, 2013 at 4:15 PM, Or Gerlitz wrote:
We've posted the kernel patches, that should be enough for the review. If you
have any specific questions re user space aspects of this series, feel free to
send them now.
Yes! for kenel space I see
as it's included in rsocket.h
Signed-off-by: Hal Rosenstock
---
diff --git a/examples/riostream.c b/examples/riostream.c
index a1d3671..6587707 100644
--- a/examples/riostream.c
+++ b/examples/riostream.c
@@ -43,7 +43,6 @@
#include
#include
-#include
#include
#include "common.h"
diff
Also, improve error 6100 log message
Signed-off-by: Hal Rosenstock
---
diff --git a/opensm/osm_db_files.c b/opensm/osm_db_files.c
index 9219722..10389da 100644
--- a/opensm/osm_db_files.c
+++ b/opensm/osm_db_files.c
@@ -162,7 +162,8 @@ int osm_db_init(IN osm_db_t * p_db, IN osm_log_t * p_log)
On 9/12/2013 4:14 AM, Line Holen wrote:
> Signed-off-by: Line Holen
Thanks. Applied.
-- Hal
--
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
On 09/12/2013 12:16 AM, David Dillow wrote:
> On Tue, 2013-09-10 at 19:44 +0200, Bart Van Assche wrote:
>> If this name was not yet in use in any interface that is visible in user
>> space, I would agree that we should come up with a better name. However,
>> the SCSI mid-layer already uses that n
On 09/12/13 18:16, Jack Wang wrote:
On 09/12/2013 12:16 AM, David Dillow wrote:
On Tue, 2013-09-10 at 19:44 +0200, Bart Van Assche wrote:
If this name was not yet in use in any interface that is visible in user
space, I would agree that we should come up with a better name. However,
the SCSI mi
> We are using the RoCE ethertype in the MAC frames, and that is all of the
> similarity between usNIC protocol and RoCE. L3 is not the GRH, but rather
> a usNIC L3 header. Customers can distinguish between RoCE traffic and
> usNIC traffic by looking at the version of the L3 frame. It is set to
On Thu, Sep 12, 2013 at 03:24:46PM +0300, Or Gerlitz wrote:
> Let me clarify this. The idea is that current RoCE applications will
> run as is after they update "their" librdmacm, since its this
> library that works with the new uverbs entries.
Or, we are not supposed to break userspace. You can'
We are using the RoCE ethertype in the MAC frames, and that is all of the
similarity between usNIC protocol and RoCE. L3 is not the GRH, but rather a
usNIC L3 header. Customers can distinguish between RoCE traffic and usNIC
traffic by looking at the version of the L3 frame. It is set to 6 for
15 matches
Mail list logo