From: Harry Butterworth Subject: Re: [PATCH 1/9] Xen Share: Simplified I/O Mechanism Date: Wed, 07 Jun 2006 14:31:13 +0100 Message-ID: <1149687074.7700.15.camel@localhost.localdomain> References: <1149572143.5183.25.camel@localhost.localdomain> <1149605249.7721.74.camel@localhost.localdomain> <1149647707.5183.186.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1149647707.5183.186.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 Wed, 2006-06-07 at 12:35 +1000, Rusty Russell wrote: > On Tue, 2006-06-06 at 15:47 +0100, Harry Butterworth wrote: > > 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? > If the > frontend or backend dies, there is no restriction on cleaning up its > memory. This is a good answer. In my use of grant-tables for the USB driver, I ended up with the possibility of one side having to poll indefinitely for the other side to free up its memory with no guarantee of this ever happening. The memory couldn't be reused until it was freed because the other side had a writeable mapping (reusing even just a readable mapping would have been a security hole). I think a fix for this problem is a significant win for your approach over grant-tables. > Hope that clarifies! Yes thanks. Harry.