All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Mark Williamson <maw48@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, Xin Zhao <zhaoxin@eecs.umich.edu>
Subject: Re: mapped memory delay?
Date: Fri, 18 Feb 2005 18:06:14 -0800	[thread overview]
Message-ID: <42169F16.4060007@diku.dk> (raw)
In-Reply-To: <200502190146.22278.maw48@cl.cam.ac.uk>

Mark Williamson wrote:
> If you're sharing memory directly between the two then you don't need to 
> involve xcs (other than in the setup phase) since that just does control 
> messages.
> 
> You might find the ring macros in xen/include/public/ring.h useful.  They make 
> it easy to declare ring datatypes (with appropriately sized rings) and 
> maintain producer / consumer indexes, with the appropriate memory barriers.
> 
> Examples of use are in linux-2.6.10-xen-sparse/drivers/xen/{blk,usb}
> {back,front}.  (the net drivers use a slightly different ring format 
> instead).

Hmm will this be any different if the guy I wish to share this with in 
dom0 is a userspace process? Can I use /dev/evtchn for that, or do I 
have to cook my own device node for this?

thanks,

Jacob


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-19  2:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18 21:44 mapped memory delay? Xin Zhao
2005-02-18 22:14 ` Christopher Clark
2005-02-18 22:41   ` Xin Zhao
2005-02-18 23:58     ` Christopher Clark
2005-02-19  1:46 ` Jacob Gorm Hansen
2005-02-19  1:46   ` Mark Williamson
2005-02-19  2:06     ` Jacob Gorm Hansen [this message]
2005-02-19  2:04       ` Mark Williamson
2005-02-19  2:46         ` Anthony Liguori
2005-02-19  3:01           ` Jacob Gorm Hansen
2005-02-19  3:26             ` Jacob Gorm Hansen

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=42169F16.4060007@diku.dk \
    --to=jacobg@diku.dk \
    --cc=maw48@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    --cc=zhaoxin@eecs.umich.edu \
    /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.