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 used >> atomic operations which depend on specific processor instructions, to >> increment a 64-bit (uint64_t) generation number. This is not possible >> on 32-bit platforms. >> >> I'm currently debating with myself and others around me, if we can be >> satisfied with using a 32-bit generation number. I used a 64-bit >> generation number, just to give us the widest possible range before >> running out. But a 32-bit generation number should be more than enough >> for normal usage. >> >> I'll update the list once we come to a decision. >> > > Let us retain support for 32-bit platforms. Though as developers we do > not run many tests on non 64-bit platforms, it would be not be good to > break compatibility for 32-bit platforms as we have many community users > running this To get rid of all this fuss, I think its better to use uint32_t instead of unint64_t. > > -Vijay > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel -- ~Atin _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
