From: Christopher J. Morrone <morrone2@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Question of transplanting Lustre to a non-x86 arch
Date: Wed, 05 Dec 2012 11:05:39 -0800 [thread overview]
Message-ID: <50BF9B03.5090402@llnl.gov> (raw)
In-Reply-To: <1a9c0f60.edf4.13b6a28a653.Coremail.eternalregion@163.com>
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@whamcloud.com> wrote:
>
> On 2012-12-04, at 0:02, Light&ColoR <eternalregion@163.com
> <mailto:eternalregion@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
> http://lists.lustre.org/mailman/listinfo/lustre-devel
>
next prev parent reply other threads:[~2012-12-05 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 7:02 [Lustre-devel] Question of transplanting Lustre to a non-x86 arch Light&ColoR
2012-12-05 3:20 ` Andreas Dilger
2012-12-05 8:22 ` Light&ColoR
2012-12-05 19:05 ` Christopher J. Morrone [this message]
2012-12-06 2:24 ` Light&ColoR
2012-12-06 21:44 ` Christopher J. Morrone
2012-12-07 2:26 ` Light&ColoR
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50BF9B03.5090402@llnl.gov \
--to=morrone2@llnl.gov \
--cc=lustre-devel@lists.lustre.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.