From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C3008A0C43; Wed, 20 Oct 2021 11:30:59 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B0FBD40687; Wed, 20 Oct 2021 11:30:59 +0200 (CEST) Received: from mail-108-mta147.mxroute.com (mail-108-mta147.mxroute.com [136.175.108.147]) by mails.dpdk.org (Postfix) with ESMTP id E540A40142 for ; Wed, 20 Oct 2021 11:30:57 +0200 (CEST) Received: from filter004.mxroute.com ([149.28.56.236] filter004.mxroute.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta147.mxroute.com (ZoneMTA) with ESMTPSA id 17c9d0a156a0000b55.001 for (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256); Wed, 20 Oct 2021 09:30:56 +0000 X-Zone-Loop: 0f00a8e83ec93f59cf8c8bd0c407710dff00405e4a49 X-Originating-IP: [149.28.56.236] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ashroe.eu; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From:References:Cc: To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=ZfOBLkNAHoaa8Ow1IwNgaQrFetDjkRhmkY0KNeBN7I8=; b=qkx/SiKojFYdj9Dum6pqPcKPuk ChkUah+dzynWegZ3WJVHSG/kQUyDqu0Zcy33IYiYAI//CccJ5ZjB2jRu116BDmR6RqdtS/F84F6r5 8OAHImbgznXr/9F9HgtzjmRp6P2SX67Bb8L5CN7M4XCEzqIoLl2YebPRlhZfWLCbQb7zn7uPReCsv bJFM+15CpKtKzpFpklWwHq5hGbB3a390fzpyNxEoj/f7XInK9XNDRcM8x86gVEE5dAWGSSYiZQlkF ahm2adiL1sTA48HOZqH/WQdwEBYhxi8AD4Pf2aBCZDO2SYPNkvq+ur/Gu+NLRKXO3rDzfC5XHGRma 2e4smZpA==; Message-ID: Date: Wed, 20 Oct 2021 10:30:52 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Content-Language: en-US To: Dmitry Kozlyuk , dev@dpdk.org Cc: Matan Azrad , Viacheslav Ovsiienko , Anatoly Burakov References: <20211013110131.2909604-1-dkozlyuk@nvidia.com> <20211015160244.3097758-1-dkozlyuk@nvidia.com> <20211015160244.3097758-4-dkozlyuk@nvidia.com> From: "Kinsella, Ray" In-Reply-To: <20211015160244.3097758-4-dkozlyuk@nvidia.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-AuthUser: mdr@ashroe.eu X-Zone-Spam-Resolution: no action X-Zone-Spam-Status: No, score=-0.1, required=15, tests=[ARC_NA=0, FROM_HAS_DN=0, TO_DN_SOME=0, MIME_GOOD=-0.1, NEURAL_SPAM=0, RCPT_COUNT_FIVE=0, RCVD_COUNT_ZERO=0, FROM_EQ_ENVFROM=0, MIME_TRACE=0, MID_RHS_MATCH_FROM=0] Subject: Re: [dpdk-dev] [PATCH v5 3/4] common/mlx5: add mempool registration facilities X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list 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 15/10/2021 17:02, Dmitry Kozlyuk wrote: > Add internal API to register mempools, that is, to create memory > regions (MR) for their memory and store them in a separate database. > Implementation deals with multi-process, so that class drivers don't > need to. Each protection domain has its own database. Memory regions > can be shared within a database if they represent a single hugepage > covering one or more mempools entirely. > > Add internal API to lookup an MR key for an address that belongs > to a known mempool. It is a responsibility of a class driver > to extract the mempool from an mbuf. > > Signed-off-by: Dmitry Kozlyuk > Acked-by: Matan Azrad > --- Acked-by: Ray Kinsella