From mboxrd@z Thu Jan 1 00:00:00 1970 From: Herbert Xu Subject: Re: RFC: [0/2] Remove netloop by lazy copying in netback Date: Tue, 27 Mar 2007 17:53:18 +1000 Message-ID: <20070327075318.GA24443@gondor.apana.org.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Isaku Yamahata , Xen Development Mailing List List-Id: xen-devel@lists.xenproject.org On Tue, Mar 27, 2007 at 08:51:15AM +0100, Keir Fraser wrote: > > Also bear in mind the plan to avoid the grant mapping at all in the > direct-to-wire transmit case. This also will rely on a #PF (or some other > fault, potentially) if the guest tries to access that pseudophysical page of > memory. If we can work out a way to make this work on ia64 then the > delayed-copy implementation problems are solved too. That's to avoid the TLB flush costs, right? On ia64 (or anything other than x86-32 for that matter) you have enough virtual address bits to map the entire physical memory into dom0 (or the driver domain) so that could also be used to avoid TLB flushes. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt