linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Neil Brown <neilb@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>, Greg Banks <gnb@sgi.com>,
	Linux NFS Mailing List <nfs@lists.sourceforge.net>,
	Linux Filesystem Mailing List <linux-fsdevel@vger.kernel.org>
Subject: Re: [NFS] [PATCH,RESEND] make knfsd interact cleanly with HSMs
Date: Mon, 8 May 2006 18:55:15 +0100	[thread overview]
Message-ID: <20060508175515.GA9662@infradead.org> (raw)
In-Reply-To: <17503.10386.171006.392544@cse.unsw.edu.au>

On Mon, May 08, 2006 at 09:16:34PM +1000, Neil Brown wrote:
> On Monday May 8, hch@infradead.org wrote:
> > NACK.  As long as we have no HSM support in the tree there's no reason to
> > add this.  From the kernel's point it's just untested and unused code that
> > can break.
> 
> 
> Greg: you seemed to suggest that there was already code in XFS that
> could make use of this.  If that is so: could you point us to it
> please.

It's used by SGI's out of tree dmapi implementation.  Because dmapi is such
an utterly braindead standard I don't expect anyone to submit a kernel-based
implementation for inclusion, although support for a big enough subset of
that standard could be archived by proper kernel <-> userspace cooperation.


  parent reply	other threads:[~2006-05-08 17:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05 11:52 [PATCH,RESEND] make knfsd interact cleanly with HSMs Greg Banks
2006-05-08  1:13 ` Neil Brown
2006-05-08  6:42 ` [NFS] " Christoph Hellwig
2006-05-08 11:16   ` Neil Brown
2006-05-08 11:37     ` Nathan Scott
2006-05-08 17:55     ` Christoph Hellwig [this message]
2006-05-09  2:35       ` Greg Banks
2006-05-09  9:19         ` Christoph Hellwig

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=20060508175515.GA9662@infradead.org \
    --to=hch@infradead.org \
    --cc=gnb@sgi.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).