linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Banks <gnb@melbourne.sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Neil Brown <neilb@suse.de>,
	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: Tue, 09 May 2006 12:35:15 +1000	[thread overview]
Message-ID: <1147142114.12319.94.camel@hole.melbourne.sgi.com> (raw)
In-Reply-To: <20060508175515.GA9662@infradead.org>

On Tue, 2006-05-09 at 03:55, Christoph Hellwig wrote:
> 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.

So your only objection is the absence of DMAPI or some equivalent?
If so, perhaps the best way forward in the short term is for SUSE
to add it as an out-of-tree patch.

> > 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

Sure it's ugly, but to be fair it's no worse than SysV semaphores
and shmem, and it does fill a real (albeit niche) need which nothing
else does AFAIK.  Compare to TLI, which is pretty much entirely useless.

>  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.

I don't understand what you mean here: surely almost all of what
DMAPI specifies is for achieving proper kernel/userspace co-operation?
Do you have some ideas for a better way of doing that?

Greg.
-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.



  reply	other threads:[~2006-05-09  2:35 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
2006-05-09  2:35       ` Greg Banks [this message]
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=1147142114.12319.94.camel@hole.melbourne.sgi.com \
    --to=gnb@melbourne.sgi.com \
    --cc=hch@infradead.org \
    --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).