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: Mon, 1 Aug 2005 07:53:19 -0400	[thread overview]
Message-ID: <20050801115319.GD6497@fieldses.org> (raw)
In-Reply-To: <20050801113954.GA8698@suse.de>

I haven't had the chance to read carefully; just one quick question:

On Mon, Aug 01, 2005 at 01:39:54PM +0200, Olaf Kirch wrote:
> +	this_page = (unsigned char *) vec[vlen-1].iov_base;
> +	for (i = vlen-1; i; --i) {
> +		prev_page = (unsigned char *) vec[i-1].iov_base;
> +
> +		/* Push trailing partial page so it's
> +		 * aligned with the end of the page, then
> +		 * pull up the missing chunk from the previous
> +		 * page */
> +		memmove(this_page + chunk0, this_page, chunk1);
> +		memcpy(this_page, prev_page + chunk1, chunk0);
> +		vec[i].iov_len = PAGE_CACHE_SIZE;
> +		this_page = prev_page;
> +	}

If there's stuff after the write data (as there could be in the NFSv4
case at least), does this overwrite it?

--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-01 11:53 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 [this message]
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
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=20050801115319.GD6497@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.