Posted changes for review,
https://review.gluster.org/10425
https://review.gluster.org/10426
~kaushal
On Tue, Apr 28, 2015 at 6:34 PM, Kaushal M kshlms...@gmail.com wrote:
After a long discussion (not really), we've concluded that a 64-bit
uint is really overkill for how we are using the
AFAIU we've not officially supported 32-bit architectures for sometime
(possibly for ever) as a community. But we had users running it
anyway.
3.7 as it is currently, cannot run on 32-bit platforms. I've used
atomic operations which depend on specific processor instructions, to
increment a 64-bit
No Raspberry Pi servers any more?
On April 28, 2015 5:07:06 AM PDT, Justin Clift jus...@gluster.org wrote:
Does this mean we're officially no longer supporting 32 bit
architectures?
(or is that just on x86?)
+ Justin
On 28 Apr 2015, at 12:45, Kaushal M kshlms...@gmail.com wrote:
Found the
On 04/28/2015 06:08 PM, Vijay Bellur wrote:
On 04/28/2015 05:48 PM, Kaushal M wrote:
AFAIU we've not officially supported 32-bit architectures for sometime
(possibly for ever) as a community. But we had users running it
anyway.
3.7 as it is currently, cannot run on 32-bit platforms. I've
On 04/28/2015 05:48 PM, Kaushal M wrote:
AFAIU we've not officially supported 32-bit architectures for sometime
(possibly for ever) as a community. But we had users running it
anyway.
3.7 as it is currently, cannot run on 32-bit platforms. I've used
atomic operations which depend on specific
After a long discussion (not really), we've concluded that a 64-bit
uint is really overkill for how we are using the generation number,
and I'll change it to a 32-bit uint. I'll send a change to do this
right away.
The generation number we use is not permanent, it is valid only within
a GlusterD
Does this mean we're officially no longer supporting 32 bit architectures?
(or is that just on x86?)
+ Justin
On 28 Apr 2015, at 12:45, Kaushal M kshlms...@gmail.com wrote:
Found the problem. The NetBSD slaves are running a 32-bit kernel and
userspace.
```
nbslave7a# uname -p
i386
```
On Tue, Apr 28, 2015 at 05:15:30PM +0530, Kaushal M wrote:
Because of this CAA_BITS_PER_LONG is set to 32 and the case for size 8
isn't compiled in uatomic_add_return. Even though the underlying
(virtual) hardware has 64-bit support, and supports the required
8-byte wide instrcution, it cannot
I seem to have found the issue.
The uatomic_add_return function is defined in urcu/uatomic.h as
```
/* uatomic_add_return */
static inline __attribute__((always_inline))
unsigned long __uatomic_add_return(void *addr, unsigned long val,
int len)
{
switch
On Tue, Apr 28, 2015 at 12:15:11PM +0530, Atin Mukherjee wrote:
I see netbsd regression doesn't execute peer probe from any other tests
apart from mgmt_v3-locks.t, if it had that would have also failed. So
the conclusion is peer probe doesn't work in netbsd. Glusterd crashes
with following bt
On Tue, Apr 28, 2015 at 12:15:11PM +0530, Atin Mukherjee wrote:
I see netbsd regression doesn't execute peer probe from any other tests
apart from mgmt_v3-locks.t, if it had that would have also failed. So
the conclusion is peer probe doesn't work in netbsd.
It does not work anymore: that
On 04/28/2015 01:24 PM, Emmanuel Dreyfus wrote:
On Tue, Apr 28, 2015 at 12:15:11PM +0530, Atin Mukherjee wrote:
I see netbsd regression doesn't execute peer probe from any other tests
apart from mgmt_v3-locks.t, if it had that would have also failed. So
the conclusion is peer probe doesn't
On 04/28/2015 01:40 PM, Emmanuel Dreyfus wrote:
On Tue, Apr 28, 2015 at 01:37:42PM +0530, Anand Nekkunti wrote:
__asm__ is for to write assembly code in c (gcc), __volatile__(:::)
compiler level barrier to force the compiler not to do reorder the
instructions(to avoid optimization ) .
13 matches
Mail list logo
