From: Olaf Kirch <okir@suse.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] Fix nfsd rewrite performance
Date: Mon, 1 Aug 2005 14:14:22 +0200 [thread overview]
Message-ID: <20050801121422.GH8698@suse.de> (raw)
In-Reply-To: <20050801121053.GA8238@fieldses.org>
On Mon, Aug 01, 2005 at 08:10:53AM -0400, J. Bruce Fields wrote:
> > Alternatively, we could pull in everything and align it with the beginning
> > of the message. This would clobber the RPC header etc. I don't see us
> > doing doing any in-place decodes of strings etc in the svcauth code,
> > so that may be a safer choice. I would like to avoid allocating an extra
> > page just for aligning things.
>
> Yeah. We'd also need to check, though, that we aren't taking pointers
> to data before the write (when decoding a previous compound op). I
> think we might be....
Can we assume that the previous op inside the compound op has been
dealt with completely? Why would it be unsafe to clobber it?
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@suse.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-08-01 12:14 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 [this message]
2005-08-01 12:58 ` J. Bruce Fields
2005-08-02 9:49 ` Olaf Kirch
2005-08-02 10:02 ` J. Bruce Fields
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=20050801121422.GH8698@suse.de \
--to=okir@suse.de \
--cc=bfields@fieldses.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