public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Geoffrey Wehrman <gwehrman@sgi.com>
To: "Larsen, Tore Høivaag" <tore.hoivaag.larsen@cggveritas.com>
Cc: Alexis Cousein <al@sgi.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: RedHat, Novell and SGI xfs kernel module api
Date: Mon, 10 Jan 2011 10:40:58 -0600	[thread overview]
Message-ID: <20110110164058.GC19571@sgi.com> (raw)
In-Reply-To: <CFFC47E79E870F4EBAD0CA24D8CD7652ED34D5BABE@CRW-EXM01.int.cggveritas.com>

On Mon, Jan 10, 2011 at 08:35:44AM +0000, Larsen, Tore Høivaag wrote:
| Hi,
| 
|     currently we are purchasing Redhat's ScaleFS, SGI's cxfs, and Novell SLES xfs.
| 
|     Having e.g. Redhat XFS play nicely with cxfs client is not trivial. Usually, I have to choose ScaleFS w/lvm2 volumes og RHEL, but if I want cxfs, But I can't have local xvm volumes on 3rd party hw. 
| 
|     Is there plans to make an effort to making sure the xfs api is common from the vendors and play nicely with each other ?    Comments? 

The community version of XFS is considered the defacto standard.  I must
compliment the community on doing an excellent job of maintaining
on-disk compatibiltiy within XFS as it has evolved.  On disk
compatibility is really the most critical API to maintain for a
filesystem.

Novell (and Red Hat) XFS will tend to lag the community top-of-tree XFS
some, as they are long life releases based on a fixed kernel version.
This somewhat restricts how much code can be backported from
top-of-tree XFS.

At SGI, we are always working on CXFS to maintain full compatibility
with community XFS.  CXFS is really just a distributed layer on top of
XFS, but we have to ship our own version of XFS with CXFS to provide all
of the interfaces requried by CXFS.  These interfaces have been removed
from community XFS as they have no purpose outside of CXFS which is SGI
proprietary software.


-- 
Geoffrey Wehrman
SGI Building 10                             Office: (651)683-5496
2750 Blue Water Road                           Fax: (651)683-5098
Eagan, MN 55121                             E-mail: gwehrman@sgi.com
	  http://www.sgi.com/products/storage/software/

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

           reply	other threads:[~2011-01-10 16:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CFFC47E79E870F4EBAD0CA24D8CD7652ED34D5BABE@CRW-EXM01.int.cggveritas.com>]

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=20110110164058.GC19571@sgi.com \
    --to=gwehrman@sgi.com \
    --cc=al@sgi.com \
    --cc=tore.hoivaag.larsen@cggveritas.com \
    --cc=xfs@oss.sgi.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox