All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Olaf Kirch <okir@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] Fix nfsd rewrite performance
Date: Tue, 2 Aug 2005 06:02:22 -0400	[thread overview]
Message-ID: <20050802100222.GA1940@fieldses.org> (raw)
In-Reply-To: <20050802094950.GB29054@suse.de>

On Tue, Aug 02, 2005 at 11:49:50AM +0200, Olaf Kirch wrote:
> I just looked at the code, and there are two types of deferrals.
> One is for authentication stuff - this will actually use svc_defer and
> svc_revisit, which goes back to look at the entire request.
> 
> The other type is what hte nfs4idmap stuff does, which uses its own
> defer/revisit routines, which just make the nfsd thread wait.
> 
> So neither poses a problem to munging the iovec in nfsd_write:

It can also happen whenever we do fh_verify().  (See the exp_find() call in
fh_verify().)

> The authentication stuff will happen when we parse the RPC header,
> which is way before we decide to call nfsd_write.  The idmap stuff may
> be called after processing a write call, but it will not go back to
> revisit the entire request, it will just stall briefly while idmapd is
> doing its job.  Correct?
> 
> In general, I believe it does not make sense to call svc_defer once
> we've started to process a request, because the request may not be
> idempotent.  It sounds like a reasonable assumption to me that
> deferring and revisiting an entire requests is only done before we hit
> the RPC program handler.

Yeah.  So the simplest solution might be to make the other upcalls use
the same sort of deferral as the idmap upcalls, at least in the v4 case.
In the v3 case fh_verify always happens early enough not to be a
problem, I believe.

Though I still think it's unfortunate even for v3 that it will try to
copy (and allocate space for) the entire write request in the case of an
authentication- or export- related upcall.

--b.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-08-02 10:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-01 11:39 [PATCH] Fix nfsd rewrite performance Olaf Kirch
2005-08-01 11:53 ` J. Bruce Fields
2005-08-01 11:59   ` Olaf Kirch
2005-08-01 12:10     ` J. Bruce Fields
2005-08-01 12:14       ` Olaf Kirch
2005-08-01 12:58         ` J. Bruce Fields
2005-08-02  9:49           ` Olaf Kirch
2005-08-02 10:02             ` J. Bruce Fields [this message]
2005-08-02 10:49               ` Olaf Kirch
2005-08-02 12:07                 ` J. Bruce Fields

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=20050802100222.GA1940@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=okir@suse.de \
    /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.