linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Jeff Layton <jlayton@redhat.com>, Tom Tucker <tom@opengridcomputing.com>
Cc: <bfields@fieldses.org>, <linux-nfs@vger.kernel.org>,
	<swise@opengridcomputing.com>, Tom Talpey <tmtalpey@gmail.com>
Subject: Re: [PATCH] svcrdma: fix offset calculation for non-page aligned sge entries
Date: Thu, 3 Apr 2014 12:43:00 +0300	[thread overview]
Message-ID: <533D2D24.40107@panasas.com> (raw)
In-Reply-To: <20140312171832.33f04ee8@tlielax.poochiereds.net>

On 03/12/2014 11:18 PM, Jeff Layton wrote:
> 
> Ok, I may need to rejigger that logic to account for that case. I'll do
> that and send a v2 once I test it out...
> 

Hi Jeff in obj-layout we have this code:

	if (*p_pgbase > PAGE_SIZE) {
		dprintk("%s: pgbase(0x%x) > PAGE_SIZE\n", __func__, *p_pgbase);
		*p_pages += *p_pgbase >> PAGE_SHIFT;
		*p_pgbase &= ~PAGE_MASK;
	}

ie. advance the page_array pointer and keep the pgbase within page.

if I recall correctly this case happens when you return a short read/write
then the retry comes again with same page_array but with base jumping over
the previous short IO, and length with the reminder.

I'm not sure what is the code path that feeds your xdr stuff but it
might not filter out the way we do in obj-lo. the ORE is the same
it assumes pgbase < PAGE_SIZE.

Cheers
Boaz


  parent reply	other threads:[~2014-04-03  9:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 14:51 [PATCH] svcrdma: fix offset calculation for non-page aligned sge entries Jeff Layton
2014-03-12 20:43 ` Tom Tucker
2014-03-12 21:18   ` Jeff Layton
2014-03-15 13:30     ` Jeff Layton
2014-03-17 17:17     ` Jeff Layton
2014-04-03  9:43     ` Boaz Harrosh [this message]
2014-04-03 11:20       ` Jeff Layton

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=533D2D24.40107@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=bfields@fieldses.org \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=swise@opengridcomputing.com \
    --cc=tmtalpey@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).