All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] [wc-discuss] Re: [Twg] Lustre and cross-platform portability
Date: Fri, 16 Mar 2012 10:46:22 -0400	[thread overview]
Message-ID: <201203161446.q2GEkNMO005460@hedwig.cmf.nrl.navy.mil> (raw)
In-Reply-To: <FC3B1D44-ED0D-4EAD-8003-B3E458A46469@xyratex.com>

>Also fuse client will able to run on any OS have a FUSE porting that is
>any BSD, OpenSolaris, MacOS, in additional to the windows.  That is
>easy way to maintain a single client for many OS.

It is, unfortunately, not quite that simple.

I can't claim to be a FUSE expert, but I've been paying attention
to it on other platforms.  From what I can tell, FUSE works great
on Linux, but on other platforms the support is iffy.  Also, it's
not quite implemented the same on other operating systems as it is
on Linux, making porting a Linux FUSE module to other platforms not
trivial; from what I've seen, this is due to the Linux filesystem
interface versus the vnode interface used by every Unix except Linux
(and this is part of what makes Lustre hard to port).

I guess what I'm saying is that don't fall into the underwear gnomes
trap of thinking:

1) Get liblustre working with FUSE
2) ???
3) Lustre client everywhere!

It might make it easier, but I doubt it will make it easy.

--Ken

  reply	other threads:[~2012-03-16 14:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15  0:31 [Lustre-devel] Lustre and cross-platform portability Andreas Dilger
2012-03-15 18:45 ` [Lustre-devel] [Twg] " Ken Hornstein
2012-03-15 19:39   ` Andreas Dilger
2012-03-15 19:51     ` Joshua Walgenbach
2012-03-16 10:11       ` [Lustre-devel] [wc-discuss] " Gregory Matthews
2012-03-16 10:35         ` Alexey Lyashkov
2012-03-16 14:46           ` Ken Hornstein [this message]
2012-03-17 10:42             ` [Lustre-devel] [wc-discuss] " Alexey Lyashkov
2012-03-16 15:06         ` [Lustre-devel] [wc-discuss] " Todd, Allen
2012-03-21 18:29           ` Nathan Rutman
2012-03-16 14:38     ` [Lustre-devel] " Ken Hornstein
2012-03-16 16:03 ` [Lustre-devel] [EXTERNAL] " Ward, Lee
     [not found] ` <5A40CBC5-F91A-4F34-8209-0C216CCE8A5D@dilger.ca>
2012-04-27  2:23   ` [Lustre-devel] [wc-discuss] " tao.peng at emc.com
2012-04-27  3:54     ` Andreas Dilger
2012-04-27 10:15       ` tao.peng at emc.com
2012-04-27 10:25         ` [Lustre-devel] [Lustre-discuss] " Roman Grigoryev
2012-04-27 12:33           ` tao.peng at emc.com
2012-05-03  9:45             ` Roman Grigoryev
2012-05-03 10:03               ` tao.peng at emc.com
2012-05-03 10:45                 ` Roman Grigoryev
2012-05-03 15:08                   ` tao.peng at emc.com
2012-04-27 20:23         ` [Lustre-devel] " Andreas Dilger
2012-04-29  4:33           ` Peng Tao
2012-04-28  8:59   ` Liang Zhen

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=201203161446.q2GEkNMO005460@hedwig.cmf.nrl.navy.mil \
    --to=kenh@cmf.nrl.navy.mil \
    --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.