From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Xen 4.0.1 "xc_map_foreign_batch: mmap failed: Cannot allocate memory" Date: Wed, 05 Jan 2011 18:10:40 +0000 Message-ID: <4D24C230020000780002A8D0@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: Charles Arnold , "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org >>> On 05.01.11 at 18:48, Stefano Stabellini wrote: > On Wed, 5 Jan 2011, Jan Beulich wrote: >> But this means it can have very close to the total amount of >> memory the guest has in flight on its own. Clearly this should >> be throttled based on available memory (just consider you have >> multiple such I/O hungry guests). >=20 > This is true in theory, but Qemu emulates a PIIX3 chipset that only has > two dma engines so I don't believe is possible to have more than 2 dma > requests in flight. > However I am not sure what is the maximum size for a single dma request. >Oh, no, we're talking about guests using pv drivers (I thought that >was said in the original mail). Rubbish. Forget that. Mixed up in my brain with something else. Jan