xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
Subject: Re: pvSCSI question - can a gref describe more than one page?
Date: Wed, 10 Mar 2010 11:18:46 -0800	[thread overview]
Message-ID: <4B97F096.8040406@goop.org> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01918CE0@trantor>

On 03/09/2010 07:18 PM, James Harper wrote:
> Porting the pvSCSI backend driver to the pvops kernel is turning out to
> be a bit harder than first thought, mostly because all the Linux
> routines that might be useful are written with the assumption that they
> would be passed a mapped buffer and they would then build an sg list out
> of that. pvSCSI already has an sg list, and all the routines that it
> makes use of have been deprecated since 2.6.18 (all the comments on the
> patches that remove the routines are like "nobody uses this anymore".
> D'oh.)
>
> The big complication appears to be that pvSCSI seems to think that an
> individual sg element can span a page, and so has to muck around
> splitting it into page-sized chunks. My assumption is that this is
> because the code in pvSCSI was cut&pasted from somewhere else.
>    

In general its a bug if an sg entry crosses a page boundary.  We define 
BIOVEC_PHYS_MERGEABLE so that we avoid doing any cross-page merges 
(unless, I think, the underlying mfns are actually contiguous).  Does 
that help?

     J

  reply	other threads:[~2010-03-10 19:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  3:18 pvSCSI question - can a gref describe more than one page? James Harper
2010-03-10 19:18 ` Jeremy Fitzhardinge [this message]
2010-03-10 22:17   ` James Harper
2010-03-25  9:55     ` Pasi Kärkkäinen

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=4B97F096.8040406@goop.org \
    --to=jeremy@goop.org \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xensource.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).