[Lustre-devel] portability in lustre code.
andreas.dilger at intel.com
Mon Sep 30 15:26:04 PDT 2013
On 2013/09/21 2:39 AM, "Alexey Lyahkov" <alexey_lyashkov at xyratex.com>
>I "happy" to see moving to lustre kernel generate a first results.
>my MacOS fuse client brooked to build after sources updates.
>In file included from
> from nidstrings.c:43:
>-bitops.h:80: error: conflicting types for Œfls¹
>/usr/include/strings.h:90: error: previous declaration of Œfls¹ was here
>that bug introduced by commit
>Author: James Simmons <uja.ornl at gmail.com>
>Date: Tue Aug 27 12:51:06 2013 -0400
> LU-1346 libcfs: cleanup macros in portals_compat25.h
>so that commit - isn't correctly inspected for systems other to linux and
>introduce a new regression for systems other then Linux.
>I was pointed about similar situation in past - but hit that in real
>Andreas, did you remember my concerns about lost portability ?
Yes, I definitely remember this discussion.
As we discussed a year ago the MacOS, Windows, and liblustre code are
currently unused, and have been unmaintained since that time. I don't
think it is reasonable for us to maintain this code for your private
FreeBSD Fuse port. The code would need to continuously built and tested
in public for it to even consider it maintained at the most basic level.
Even prior to this recent compile problem, I would be incredibly surprised
if this code was working. The liblustre code has been unmaintained since
Oracle times, and the Windows client has never been publicly released.
If MacOS _was_ working under your testing, it would have made sense to
share this code publicly last year.
>batch changes code in way without ability to replace a cfs specific
>function to any existent in build env. and we don't have a way to the
>replace fls with flsl for MacOS/BSD or use own implementation without
>reverting a cleanup for fls function.
It would be fairly straight forward for you to apply a patch or run the
code through a sed script before build to replace the few conflicting names
with their equivalent MacOS functions. This could be similar to how
ldiskfs is built from the ext4 code.
You are of course also free to keep a private or public branch of the code
for your own use. We were planning to deleting the liblustre, MacOS, and
WinNT code entirely from the repository in the next release, because it is
unused and causes an ongoing maintenance and development complexity for
the Linux code without any benefit. In particular, the abstractions in
CLIO are far more complex than they need to be for just Linux clients
because the Linux and MacOS VM/VFS interfaces are wildly different.
Lustre Software Architect
Intel High Performance Data Division
More information about the lustre-devel