From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Burakov, Anatoly" Subject: Re: [PATCH v2 1/6] mem: add function for checking memsegs IOVAs addresses Date: Fri, 5 Oct 2018 13:15:10 +0100 Message-ID: References: <1538741212-7922-1-git-send-email-alejandro.lucero@netronome.com> <1538741212-7922-2-git-send-email-alejandro.lucero@netronome.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit To: Alejandro Lucero , dev@dpdk.org Return-path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 0D2F6239 for ; Fri, 5 Oct 2018 14:15:12 +0200 (CEST) In-Reply-To: <1538741212-7922-2-git-send-email-alejandro.lucero@netronome.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 05-Oct-18 1:06 PM, Alejandro Lucero wrote: > A device can suffer addressing limitations. This function checks > memsegs have iovas within the supported range based on dma mask. > > PMDs should use this function during initialization if device > suffers addressing limitations, returning an error if this function > returns memsegs out of range. > > Another usage is for emulated IOMMU hardware with addressing > limitations. > > It is necessary to save the most restricted dma mask for checking out > memory allocated dynamically after initialization. > > Signed-off-by: Alejandro Lucero > --- Reviewed-by: Anatoly Burakov -- Thanks, Anatoly