All of lore.kernel.org
 help / color / mirror / Atom feed
From: NAHieu <nahieu@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Anton Korenyushkin <tiger@swsoft.mipt.ru>
Subject: Re: back/frontend drivers HelloWorld
Date: Fri, 23 Sep 2005 18:53:17 +0900	[thread overview]
Message-ID: <5d7aca9505092302532b4e88eb@mail.gmail.com> (raw)
In-Reply-To: <fca75d25983158236837abcbeb5c6af7@cl.cam.ac.uk>

On 9/22/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
>
> On 22 Sep 2005, at 14:46, Anton Korenyushkin wrote:
>
> >
> > I'm reading blkback/front driver's code, but it is too complicated.
> > I've
> > understood that i should use message rings for my task (i've read
> > docs/misc/blkif-drivers-explained.txt too). But how to get such ring?
> >
> > May be a simple example of solution such problem exists, so could you
> > point me
> > on this example?
>
> You bootstrap yourself via xenbus. You have a pre-agreed location in
> the xenstore hieararchy where the frontend driver writes key-value
> pairs containing the grant reference for the page containing the
> message rings, and an event channel for async notifications.
>

I imagine that we can get rid of event channel, and use xenstore to
notify. That is certainly OK, but I doubt about its efficientcy. What
do you think?

Thanks,
NAH

  reply	other threads:[~2005-09-23  9:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 13:46 back/frontend drivers HelloWorld Anton Korenyushkin
2005-09-22 14:18 ` Keir Fraser
2005-09-23  9:53   ` NAHieu [this message]
2005-09-23 10:00     ` Keir Fraser
2005-09-23 11:37       ` NAHieu
2005-09-23 11:54         ` Keir Fraser
2005-09-23 12:37           ` NAHieu
2005-09-23 13:40             ` Keir Fraser
2005-09-24 17:40       ` NAHieu
2005-09-24 19:31         ` Keir Fraser
2005-09-25 16:24           ` NAHieu
2005-09-25 18:56             ` Keir Fraser
2005-09-26  1:38               ` NAHieu
2005-09-26  7:19                 ` Keir Fraser
2005-09-22 16:04 ` Mark Williamson

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=5d7aca9505092302532b4e88eb@mail.gmail.com \
    --to=nahieu@gmail.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=tiger@swsoft.mipt.ru \
    --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.