From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33158) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ahpbq-0005Fg-RM for qemu-devel@nongnu.org; Sun, 20 Mar 2016 22:30:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ahpbn-00078z-MH for qemu-devel@nongnu.org; Sun, 20 Mar 2016 22:30:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:44010) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ahpbn-00078j-H3 for qemu-devel@nongnu.org; Sun, 20 Mar 2016 22:30:19 -0400 Date: Mon, 21 Mar 2016 10:30:12 +0800 From: Peter Xu Message-ID: <20160321023012.GA4468@pxdev.xzpeter.org> References: <56E70871.3050305@gmail.com> <20160315085236.GA23495@pxdev.xzpeter.org> <20160318030643.GI23495@pxdev.xzpeter.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH][RFC] IOMMU: Add Support to VFIO devices with vIOMMU present List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Aviv B.D." Cc: marcel@redhat.com, Jan Kiszka , Alex Williamson , qemu-devel@nongnu.org, "Michael S. Tsirkin" On Sat, Mar 19, 2016 at 11:40:04AM +0200, Aviv B.D. wrote: [...] > As far as I understand the code, currently there is no way to turn off the > IOTLB. > Furthermore. the IOTLB is not implemented as LRU, and actually caches > (indefinitely) > any accessed address, without any size constrains. I use those assumptions > to know > whether the current invalidation is for unmap operation or map operation. Please have a look at VTD_IOTLB_MAX_SIZE. It seems to be the size of the hash. Btw, I guess it's a much bigger problem if IOTLB has unlimited cache size... Thanks. -- peterx