From: Greg Banks <gnb@sgi.com>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: neilb@suse.de, bfields@fieldses.org, nfs@lists.sourceforge.net
Subject: Re: [RFC,PATCH] svc: Add xprt header len to svc_deferred_req
Date: Wed, 10 Oct 2007 12:47:04 +1000 [thread overview]
Message-ID: <20071010024704.GD20690@sgi.com> (raw)
In-Reply-To: <1191983661.16714.19.camel@trinity.ogc.int>
On Tue, Oct 09, 2007 at 09:34:21PM -0500, Tom Tucker wrote:
> On Wed, 2007-10-10 at 12:39 +1000, Greg Banks wrote:
> > On Tue, Oct 09, 2007 at 05:57:40PM -0500, Tom Tucker wrote:
> > >
> > Are you planning on restoring rqstp->rq_xprt_hlen from
> > dr->xprt_hlen in svc_deferred_recv() ?
>
> Well that's a really good question. I'm assuming RPC are never deferred
> more than one. That seems naive looking at the code.
Also, multiple other RPCs can be handled by the nfsd thread while
waiting for deferred RPCs, each of which can change rq_xprt_hlen
to different values.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
Apparently, I'm Bedevere. Which MPHG character are you?
I don't speak for SGI.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-10-10 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 22:57 [RFC,PATCH] svc: Add xprt header len to svc_deferred_req Tom Tucker
2007-10-10 2:39 ` Greg Banks
2007-10-10 2:34 ` Tom Tucker
2007-10-10 2:47 ` Greg Banks [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=20071010024704.GD20690@sgi.com \
--to=gnb@sgi.com \
--cc=bfields@fieldses.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=tom@opengridcomputing.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 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.