From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-f194.google.com (mail-pg1-f194.google.com [209.85.215.194]) by dpdk.org (Postfix) with ESMTP id 6392B1BCC2 for ; Thu, 20 Dec 2018 17:16:50 +0100 (CET) Received: by mail-pg1-f194.google.com with SMTP id v28so1097827pgk.10 for ; Thu, 20 Dec 2018 08:16:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=w5rwNLZOq1U8XWGiLHFmZiXh0VdH+PnHsUnlCrQIIGI=; b=0UQDAsxI03+ZmBD0gA7nhXAkukgvDSOYZ6R8TXKKukiFIrfb2gtQoVUBBTaKObzo5h tlR3HyWvqrklKQIjCO6t/+oawepLnb6lZsA5/qEALPDAaf+3HQVyltoBYPsxQKqYmyIM tv784wQjpVPIcCjbSebsrg7Cwy5wX2PT5g+PKfIXM2nDPz/ByOvq7/Agl/VzkRB5KtKr sUrgptZZ5uzF8S3+/Ml05y7zkG5z8fTMFc4DimNgnUWb/IxBj/PkdUANDTpJiQeyd68J jQHbqmPByABDzF2PMrE4OesveNOhDQ5j+i9zOc2BDm//OYANLDK4T7LqCPQy3MK52Fvb Uffw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=w5rwNLZOq1U8XWGiLHFmZiXh0VdH+PnHsUnlCrQIIGI=; b=BSO/87jF2OKfkbYqDRuUuPuMy3vVEsunbHny/jm3VxOXvF/82jj8SJp94v9xSkDPpr Rv+b8Ix+MVm0irdboUEp1G8qNsWiyUQ0uwIJd18QCDvLRE6wLFSua4DHu6EPvkQinzBP M6XBPCcYwOzFmlEPb3W/LLlOSCjgo59cWVwMRIxPSoIjNLywlp/Fa2yJcoqi4tW3HgKM GejpunHZKXHsI6unSBP4jzXzhHCf1JZ/6lIlH2wOf2DXF2jXNOSNR6TaFfMjOAx7aYS5 QMuf2uYn1FDPSrxf+NNUcBkEznnNdYnUc2M3EwKMWHLvgzn4wrChVpsVwS46AHwBDb3Z kQ3A== X-Gm-Message-State: AA+aEWae304x7Iiuh9mEw8kCIBm8eT/jPaFPraBk0/jGR2snY94EmBsD UeHJtJvJCFJ7Ri4kQDhnMhbzAQ== X-Google-Smtp-Source: AFSGD/Xwb3wWOb8z39UbvQTo0WswcUlVLIuRjaZY+I+WY0TGXdEPY8yXV46qssUVD7UGhvLo7DgL1g== X-Received: by 2002:a65:6684:: with SMTP id b4mr23735857pgw.55.1545322609229; Thu, 20 Dec 2018 08:16:49 -0800 (PST) Received: from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id x27sm41616549pfe.178.2018.12.20.08.16.48 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 20 Dec 2018 08:16:49 -0800 (PST) Date: Thu, 20 Dec 2018 08:16:46 -0800 From: Stephen Hemminger To: Anatoly Burakov Cc: dev@dpdk.org, shahafs@mellanox.com, yskoh@mellanox.com, thomas@monjalon.net, shreyansh.jain@nxp.com Message-ID: <20181220081646.55593779@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v3 0/4] Allow using external memory without malloc X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 16:16:50 -0000 On Thu, 20 Dec 2018 15:32:37 +0000 Anatoly Burakov wrote: > Currently, the only way to use externally allocated memory > is through rte_malloc API's. While this is fine for a lot > of use cases, it may not be suitable for certain other use > cases like manual memory management, etc. > > This patchset adds another API to register memory segments > with DPDK (so that API's like ``rte_mem_virt2memseg`` could > be relied on by PMD's and such), but not create a malloc > heap out of them. > > Aside from the obvious (not adding memory to a heap), the > other major difference between this API and the > ``rte_malloc_heap_*`` external memory functions is the fact > that no DMA mapping is performed automatically, as well as > no mem event callbacks are triggered. > > This really draws a line in the sand, and there are now two > ways of doing things - do everything automatically (using > the ``rte_malloc_heap_*`` API's), or do everything manually > (``rte_extmem_*`` and future DMA mapping API [1] that would > replace ``rte_vfio_dma_map``). This way, the consistency of > API is kept, and flexibility is also allowed. > > [1] https://mails.dpdk.org/archives/dev/2018-November/118175.html Where are the examples for this? Give a sample application maybe. Also there are no test cases.