From: Pete Wyckoff <pw@osc.edu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Bob Smart <smart@hpc.CSIRO.AU>,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: handling NFSERR_JUKEBOX
Date: Thu, 8 Nov 2001 11:20:10 -0500 [thread overview]
Message-ID: <20011108112010.C5145@osc.edu> (raw)
In-Reply-To: <200111061036.VAA07886@trout.hpc.CSIRO.AU> <shsg07sknsf.fsf@charged.uio.no> <shs4ro7a2n2.fsf_-_@charged.uio.no>
In-Reply-To: <shs4ro7a2n2.fsf_-_@charged.uio.no>; from trond.myklebust@fys.uio.no on Wed, Nov 07, 2001 at 12:41:21AM +0100
trond.myklebust@fys.uio.no said:
> > I'm still not convinced this is a good idea, but if you are
> > going to do things inside the NFS client, why don't you instead
> > write a wrapper function around rpc_call_sync() for
> > fs/nfs/nfs3proc.c. Something like
>
> ...and here's the full patch that implements it...
Works like a charm. Glad you allowed yourself to be badgered
into writing the proper code to handle EJUKEBOX. I'll destroy
my icky version.
Can you push it forward to Linus for general inclusion?
-- Pete
prev parent reply other threads:[~2001-11-08 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 0:23 handling NFSERR_JUKEBOX Bob Smart
2001-07-13 14:06 ` Pete Wyckoff
2001-11-06 5:21 ` Red Hat needs this patch (was Re: handling NFSERR_JUKEBOX) Bob Smart
2001-11-06 9:05 ` Trond Myklebust
2001-11-06 9:10 ` Marcelo Tosatti
2001-11-06 10:53 ` Trond Myklebust
2001-11-06 10:36 ` Bob Smart
2001-11-06 13:54 ` Trond Myklebust
2001-11-06 23:41 ` handling NFSERR_JUKEBOX Trond Myklebust
2001-11-08 16:20 ` Pete Wyckoff [this message]
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=20011108112010.C5145@osc.edu \
--to=pw@osc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=smart@hpc.CSIRO.AU \
--cc=trond.myklebust@fys.uio.no \
/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.