it is possible to get around the limitations of the Phi in this area
by having an IB card in the set up and configuring Gluster to use it.
On Thu, Apr 2, 2015 at 4:10 PM, Justin Clift wrote:
> On 12 Feb 2015, at 08:54, Mohammed Rafi K C wrote:
>> On 02/12/2015 08:32 AM, Rudra Siva wrote:
>>> Ra
On 12 Feb 2015, at 08:54, Mohammed Rafi K C wrote:
> On 02/12/2015 08:32 AM, Rudra Siva wrote:
>> Rafi,
>>
>> I'm preparing the Phi RDMA patch for submission
>
> If you can send a patch to support iWARP, that will be a great addition
> to gluster rdma.
Clearing out older email... did this patc
On 02/12/2015 08:32 AM, Rudra Siva wrote:
> Rafi,
>
> I'm preparing the Phi RDMA patch for submission
If you can send a patch to support iWARP, that will be a great addition
to gluster rdma.
> - definitely
> performance is better with the buffer pre-registration fixes. My patch
> will be witho
Rafi,
I'm preparing the Phi RDMA patch for submission - definitely
performance is better with the buffer pre-registration fixes. My patch
will be without your fixes and doesn't rely on your enhancements so it
can come in at any time. There are two default values that Phi
generally has a problem wi
In rdma.c : gf_rdma_do_reads : pthread_mutex_lock
(&priv->write_mutex); - lock guards against what?
On Mon, Feb 9, 2015 at 1:10 AM, Mohammed Rafi K C wrote:
>
> On 02/08/2015 07:52 PM, Rudra Siva wrote:
>> Thanks for trying and sending the changes - finally got it all working
>> ... it turned ou
On 02/08/2015 07:52 PM, Rudra Siva wrote:
> Thanks for trying and sending the changes - finally got it all working
> ... it turned out to be a problem with my changes (in
> gf_rdma_post_unref - goes back to lack of SRQ on the interface)
>
> You may be able to simulate the crash if you set volume p
Thanks for trying and sending the changes - finally got it all working
... it turned out to be a problem with my changes (in
gf_rdma_post_unref - goes back to lack of SRQ on the interface)
You may be able to simulate the crash if you set volume parameters to
something like the following (it would
On 02/06/2015 05:31 AM, Rudra Siva wrote:
> Rafi,
>
> Sorry it took me some time - I had to merge these with some of my
> changes - the scif0 (iWARP) does not support SRQ (max_srq : 0) so have
> changed some of the code to use QP instead - can provide those if
> there is interest after this is sta
Rafi,
Sorry it took me some time - I had to merge these with some of my
changes - the scif0 (iWARP) does not support SRQ (max_srq : 0) so have
changed some of the code to use QP instead - can provide those if
there is interest after this is stable.
Here's the good -
The performance with the patc
Adding LEXLIB= works.
bison supports -p however the output from the build is different than
when I do bison -y -p ...
>From bison -y -p .. y.tab.c looks as follows:
#define yylex graph.yylex
>From standard configure bison output:
#define yylex graphyylex
Looks like the sta
On 01/29/2015 06:13 PM, Rudra Siva wrote:
> Hi,
>
> Have been able to get Gluster running on Intel's MIC platform. The
> only code change to Gluster source was an unresolved yylex (I am not
> really sure why that was coming up - may be someone more familiar with
> it's use in Gluster can answer).
On 01/29/2015 09:12 AM, Kaushal M wrote:
tl;dr: Add a 'LEXLIB=' flag to your configure command, ie. `./configure
LEXLIB=`
This is problem with flex-2.5.38 and above. From this version, flex
generates a shared library in its default build (libfl.so). This shared
object doesn't actually conta
tl;dr: Add a 'LEXLIB=' flag to your configure command, ie. `./configure
LEXLIB=`
This is problem with flex-2.5.38 and above. From this version, flex
generates a shared library in its default build (libfl.so). This shared
object doesn't actually contain any exported symbols (AFAIK).
Automake/
On 01/29/2015 07:43 AM, Rudra Siva wrote:
Hi,
Have been able to get Gluster running on Intel's MIC platform. The
only code change to Gluster source was an unresolved yylex (I am not
really sure why that was coming up - may be someone more familiar with
it's use in Gluster can answer).
At the st
Hi,
Have been able to get Gluster running on Intel's MIC platform. The
only code change to Gluster source was an unresolved yylex (I am not
really sure why that was coming up - may be someone more familiar with
it's use in Gluster can answer).
At the step for compiling the binaries (glusterd, glu
15 matches
Mail list logo
