All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: FIFO-based event channel ABI design (draft B)
Date: Mon, 18 Feb 2013 15:19:26 +0000	[thread overview]
Message-ID: <1361200766.1051.5.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <511E46FD.3010605@citrix.com>

On Fri, 2013-02-15 at 14:32 +0000, David Vrabel wrote:
> Except for a lack of information of the required memory barriers (to be
> included in draft C), this should now be completely enough to start on a
> prototype (any volunteers? ;).

I think the real question is whether you as creator of the design are
going to be working on the implementation. That would the usual
progression of things.

As I see it we have on the one hand a substantially complete
implementation of one solution and a design draft of the other with
nobody signed up to even implement a prototype at the moment.

Given that I think we should surely go with the available solution for
4.3, which does meet our current needs AFAICT (most of the stuff which
the other design adds is gravy AFAICT). If something better comes along
(be that the FIFO design or something else) in the future then we can
consider it on its merits then.

Ian.

  parent reply	other threads:[~2013-02-18 15:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 14:32 FIFO-based event channel ABI design (draft B) David Vrabel
2013-02-15 15:05 ` Jan Beulich
2013-02-15 15:17   ` David Vrabel
2013-02-15 15:36     ` Jan Beulich
2013-02-15 18:19 ` Wei Liu
2013-02-15 18:46   ` David Vrabel
2013-02-15 19:04     ` Wei Liu
2013-02-18  8:10     ` Jan Beulich
2013-02-18 15:19 ` Ian Campbell [this message]
2013-02-18 20:16   ` David Vrabel
2013-02-18 20:50     ` Wei Liu
2013-02-18 20:21   ` Keir Fraser
2013-02-19 18:39 ` Ian Jackson

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=1361200766.1051.5.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=wei.liu2@citrix.com \
    --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.