On Sun, 28 Jul 2013, Li Wang wrote: > Personally, I think it may be more important to improve portability of Ceph at > the architecture level. For example, the coming ARM64 support, > ARM has proven its name for its low power etc, it shoule be extremely suitable > for running IO extensive application like Ceph. > > Does Inktank or any other party have plan on that? We would be very > interesting in that, and pleasure to contribute. We do! We are working closely with Calxeda to fully support their current generation of ARM processors, and Ceph+ARM solutions are already available in the marketplace. Once the 64-bit processors are available we will be testing on those as well. At this point, most of the portability work is complete. There are still opportunities for ARM-specific optimization (e.g., optimizing crc32c), but moving forward I think most of the focus will be on generic optimization: reducing CPU utilization to support both high-IOPS workloads and low power processors. This would be another good topic to discuss at CDS! sage > > On 07/27/2013 11:35 PM, Sage Weil wrote: > > On Sat, 27 Jul 2013, Li Wang wrote: > > > We did some work on Sparc machine, fixed some little endian/big endian as > > > well > > > as non-align access issues. We are using CentOS 6 recompiled version. We > > > have > > > managed to compile Ceph, however, it still could not work properly due to > > > some > > > aotmic function bug from some libs. We did not track it further recently. > > > > > > Any experiences on running Ceph on big endian machine to share? > > > > We built on a PPC machine a while back and used that to verify that the > > big/little endian stuff was working. We don't have any big endian > > machines in our lab to let us verify this on an ongoing basis, however. > > I'm not sure what the best options are to do that... qemu? > > > > We'd love to see what endian issues you did hit, by the way, to make sure > > they make into the tree! > > > > sage > > > > > > > > > > On 07/27/2013 07:07 AM, Noah Watkins wrote: > > > > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/Increasing_Ceph_portability > > > > > > > > Recently I've managed to get Ceph built and running on OSX. There was > > > > a past effort to get Ceph working on non-Linux platforms, most notably > > > > FreeBSD, but that approach introduced a lot of ad-hoc macros that has > > > > made it difficult to manage changes needed to support additional > > > > platforms. > > > > > > > > This session would address the areas within Ceph that are currently > > > > non-portable, discuss the state of OSX support, and touch on what is > > > > needed to factor out platform specific functionality. Changes are > > > > roughly grouped into (1) internal critical (e.g. locking) (2) internal > > > > non-critical (some optimizations), and (2) exported headers. A > > > > significant amount of the OSX changes have been introduced as feature > > > > tests with generic alternatives, and as such the tree may already be > > > > near building on additional platforms, so it would be great to find > > > > people that would be willing to test on additional platforms. > > > > > > > > If you are interested please add yourself as an interested party or > > > > owner of this blueprint :) > > > > -- > > > > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > > > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > > > > -- > > > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > > > > > > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
