From: Harry Butterworth Subject: Re: [PATCH 1/9] Xen Share: Simplified I/O Mechanism Date: Tue, 06 Jun 2006 15:47:29 +0100 Message-ID: <1149605249.7721.74.camel@localhost.localdomain> References: <1149572143.5183.25.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1149572143.5183.25.camel@localhost.localdomain> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Rusty Russell Cc: Xen Mailing List List-Id: xen-devel@lists.xenproject.org On Tue, 2006-06-06 at 15:35 +1000, Rusty Russell wrote: > This introduces a page "share" mechanism to xen: an alternative to > both cross-domain binding of event channels, and grant tables. Why do you think an alternative to event channels and grant tables is needed? Personally, I think there is a need for a more convenient _high-level_ API that more directly meets the split-drivers' requirements for inter-domain messaging and bulk data transfer but this seems to me to be another low-level API and doesn't seem significantly more convenient to use than grant-tables and event-channels. Is the n>2-way sharing feature the only benefit over grant-tables or do you think there are other benefits to your approach?