[Lustre-devel] Question of transplanting Lustre to a non-x86 arch
Christopher J. Morrone
morrone2 at llnl.gov
Thu Dec 6 13:44:22 PST 2012
I make it my doing something like this:
sh autogen.sh && ./configure && make rpms
I'll assume that you are running Linux, and only want to build the
Looking at Lustre's master branch, I'm not seeing 100+ lines of assembly
in the main code. Most of the assembly seems to be in code for darwin
OS and windows, and you can just ignore that.
It looks like commit 5a562259fce98b15f519fab7dd8cb921e8445d7b might be a
problem for you. There is a sloppy architecture check in the automake file:
+AM_CONDITIONAL(ARCH_x86, test x$target_cpu != "xpowerpc")
In my opinion, the files really should have been put in an
architecture-specific subdirectory too.
The only other place I see assembly is in the a patch for the kernel,
and if you are only running Linux clients, you don't need the kernel
To compile lustre without the server code, you'll want this configure
On 12/05/2012 06:24 PM, Light&ColoR wrote:
> Wow! BTW, how did you make it? Actually I wanna use Lustre on MIPS. Taking a quicklook at Lustre sources, I just find less than 100 lines architecture-sepcific asm codes( maybe more). It's should not be hard to transplant Lustre.......
> At 2012-12-06 03:05:39,"Christopher J. Morrone" <morrone2 at llnl.gov> wrote:
>> Just FYI, we have been successfully using Lustre clients on PowerPC
>> architectures at LLNL for years, and PowerPC has a different default
>> page size and endianness than x86.
>> On 12/05/2012 12:22 AM, Light&ColoR wrote:
>>> Big thx to you Andreas!
>>> At 2012-12-05 11:20:17,"Andreas Dilger" <adilger at whamcloud.com> wrote:
>>> On 2012-12-04, at 0:02, Light&ColoR <eternalregion at 163.com
>>> <mailto:eternalregion at 163.com>> wrote:
>>>> I am a newbie, I have a little bit of experience in linux kernel,
>>>> but not transplanting Lustre. How should I identify which part of
>>>> source code in Lustre is architecture specified?
>>> There is not much architecture-specific code in Lustre, and the less
>>> the better...
>>> Probably the easiest is to just try compiling it and seeing where
>>> the issues are. Some are in the build system -we don't have configs
>>> for server kernels. That isn't needed on the client though.
>>> Big endian severs are not really supported as we have no ability to
>>> test or fix them.
>>> Please keep the list updated with your progress, since this has been
>>> asked a couple of times here recently.
>>> Cheers, Andreas
>>> Lustre-devel mailing list
>>> Lustre-devel at lists.lustre.org
>> Lustre-devel mailing list
>> Lustre-devel at lists.lustre.org
More information about the lustre-devel