All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike D. Day" <ncmike@us.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Xen Mailing List <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1/9] Xen Share: Simplified I/O Mechanism
Date: Wed, 14 Jun 2006 13:46:37 -0400	[thread overview]
Message-ID: <44904B7D.8070802@us.ibm.com> (raw)
In-Reply-To: <1149572143.5183.25.camel@localhost.localdomain>

Rusty Russell wrote:
> Finally, a scatter-gather list mechanism allows the domains to
> associate their pages with arbitrary queue numbers in the shared
> region, to transport bulk data (effectively by having the hypervisor
> do "DMA" between domains).

The sg transfer mechanism avoids bounce buffers and does a straight copy 
  from_user or to_user below. So this is an alternative to page 
flipping, right? It would be interesting to see how the direct copy 
performs compared to page flipping on various architectures. Page table 
updates are not free and processors are getting more efficient at bulk dma.

> > +/* Copy from src to dst, return amount copied. */
> +static int do_copy(const struct sg_list *sgdst, const struct sg_list *sgsrc,
> +		   unsigned long (*copy)(paddr_t, paddr_t, unsigned long))
> +{
> +	unsigned long totlen, src, dst, srcoff, dstoff;
> +	int ret = 0;
> +
> +	totlen = 0;
> +	src = dst = 0;
> +	srcoff = dstoff = 0;
> +	while (src < sgsrc->num_sg) {
> +		unsigned long len;
> +		len = min(sgsrc->sg[src].len - srcoff,
> +			  sgdst->sg[dst].len - dstoff);
> +
> +		len = copy(sgdst->sg[dst].addr+dstoff,
> +			   sgsrc->sg[src].addr+srcoff,
> +			   len);

      parent reply	other threads:[~2006-06-14 17:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06  5:35 [PATCH 1/9] Xen Share: Simplified I/O Mechanism Rusty Russell
2006-06-06  5:50 ` [PATCH 3/9] privcmd interface addition to support share operations from Dom0 userspace Rusty Russell
2006-06-06  5:51 ` [PATCH 4/9] /dev/xenshare for accessing/mapping shared pages from userspace Rusty Russell
2006-06-06  5:52 ` [PATCH 5/9] Vdevice share in start_info Rusty Russell
2006-06-06  5:54 ` [PATCH 6/9] Linux support for vdevice bus Rusty Russell
2006-06-07 10:03   ` Jacob Gorm Hansen
2006-06-07 10:58     ` Rusty Russell
2006-06-07 11:09       ` Jacob Gorm Hansen
2006-06-06  5:55 ` [PATCH 7/9] vdevice tool for manipulating " Rusty Russell
2006-06-06  5:57 ` [PATCH 8/9] Xen Share Net Device Rusty Russell
2006-06-06  5:58 ` [PATCH 2/9] Linux kernel infrastructure for Xen Share access Rusty Russell
2006-06-14 17:26   ` Mike D. Day
2006-06-06  5:59 ` [PATCH 9/9] Simple Xenshare Block Device and userspace backend Rusty Russell
2006-06-06 14:31 ` [PATCH 1/9] Xen Share: Simplified I/O Mechanism Harry Butterworth
2006-06-07  2:24   ` Rusty Russell
2006-06-06 14:47 ` Harry Butterworth
2006-06-07  2:35   ` Rusty Russell
2006-06-07 13:31     ` Harry Butterworth
2006-06-14 17:46 ` Mike D. Day [this message]

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=44904B7D.8070802@us.ibm.com \
    --to=ncmike@us.ibm.com \
    --cc=rusty@rustcorp.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 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.