From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Law Subject: Re: RFC -- virtualisable NIC support in Xen Date: Fri, 22 Sep 2006 12:04:38 +0100 Message-ID: <4513C346.6070209@solarflare.com> References: <54AD0F12E08D1541B826BE97C98F99F1A30F2F@NT-SJCA-0751.brcm.ad.broadcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54AD0F12E08D1541B826BE97C98F99F1A30F2F@NT-SJCA-0751.brcm.ad.broadcom.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Caitlin Bestler Cc: xen@solarflare.com, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Caitlin Bestler wrote: > When the App/DomU posts a buffer (for TX or RX), > what address does it use, and how does the hardware > understand it? It uses a "buffer address". This is essentially an index into a "buffer-table" which is stored on the NIC. This table is used to lookup physical addresses that the NIC will DMA to/from. The buffer-table is programmed from Dom0. The buffer-table is effectively our IOMMU/page-tables. Hope this helps, Greg -- Greg Law glaw@solarflare.com +44 1223 518 040