linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Greg Banks <gnb@sgi.com>
Cc: Linux NFS Mailing List <nfs@lists.sourceforge.net>,
	Linux Filesystem Mailing List <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH,RESEND] make knfsd interact cleanly with HSMs
Date: Mon, 8 May 2006 11:13:06 +1000	[thread overview]
Message-ID: <17502.39714.775234.337995@cse.unsw.edu.au> (raw)
In-Reply-To: message from Greg Banks on Friday May 5

On Friday May 5, gnb@sgi.com wrote:
> 
> This patch seeks to remedy the interaction between knfsd and HSMs by
> providing mechanisms to allow knfsd to tell an underlying filesystem
> (which supports HSMs) not to block for reads, writes and truncates
> of offline files.  It's a port of a Linux 2.4 patch used in SGI's
> ProPack distro since 2004 and in SLES9 since SP2.  The patch:
> 
> *  provides a new ATTR_NO_BLOCK flag which the kernel can
>    use to tell a filesystem's inode_ops->setattr() operation not
>    to block when truncating an offline file.  XFS already obeys
>    this flag (inside a #ifdef)
> 
> *  changes knfsd to provide ATTR_NO_BLOCK when it does the VFS
>    calls to implement the SETATTR NFS call.
> 
> *  changes knfsd to supply the O_NONBLOCK flag in the temporary
>    struct file it uses for VFS reads and writes, in order to ask
>    the filesystem not to block when reading or writing an offline
>    file.  XFS already obeys this new semantic for O_NONBLOCK
>    (and in SLES9 so does JFS).
> 
> *  adds code to translate the -EAGAIN the filesystem returns when
>    it would have blocked, to the -ETIMEDOUT that knfsd expects.
> 

Yes, I'm happy with this.  All the changes make sense and look right.

Thanks for persisting with it.

I'll send it on up the chain...

NeilBrown


  reply	other threads:[~2006-05-08  1:13 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 [this message]
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
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=17502.39714.775234.337995@cse.unsw.edu.au \
    --to=neilb@suse.de \
    --cc=gnb@sgi.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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).