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 47C1AA00C4; Thu, 30 Jun 2022 18:45:45 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D4D924069D; Thu, 30 Jun 2022 18:45:44 +0200 (CEST) Received: from mail-pg1-f176.google.com (mail-pg1-f176.google.com [209.85.215.176]) by mails.dpdk.org (Postfix) with ESMTP id C94C540694 for ; Thu, 30 Jun 2022 18:45:42 +0200 (CEST) Received: by mail-pg1-f176.google.com with SMTP id 9so19017739pgd.7 for ; Thu, 30 Jun 2022 09:45:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=36lWGp4VWN+OED8w2QmZqKh8QN5WP+jlhsvQsVA5K64=; b=MfeR7t/sEzZ+GzzmrqI696DkFV0f7iZnjvqK1VJCXEYbHtFd9iXzktqBiBykCE9+LZ CKq1MYB9kvq0WWCTcEPvXcEv81Tfoxk8kVOGytDj/1IbYQ+fhLgAwNKrUx8S+kubyV3D 5id6BpMZKwyxAvOBKhogWybZ9IfMnNY2vaiH5RIQEug6ZHoFWBf2A9aIVSB+EZGPYE37 f0rAKBqU8/ArwUA7/DkwHInLq4AiQ8VLyrdhVW0PLgPd8HbdzvNP4M5uBePMLPRPj2pg Rg8j+9phr/29VWqwwGkkyaqld7GkJqlf1YuZQZrFSH+n9WaR7103xQeiA1daZ9ZWFWxi D2IQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=36lWGp4VWN+OED8w2QmZqKh8QN5WP+jlhsvQsVA5K64=; b=ljMffNpfa/3DwBzGFi8M+quzlLE0AwQUr7MkPbf7Cbl07GrDJQpz3wx90vCO8h2Wx3 40cTZfTPps2LBWstDakznTt2OWHG49OyqLnmGVZ7mQnojvIbKSgqmluwpKFGBZzIgYnS AtQ7Yv3sf2pEQ+jSTz8Bd+N9UIwdUJNDGyO+NUNo0bkbQMhJjLndeM5NfEAaLtuodTl0 RURx1fzptlULZYwhgD4+5BR6n3Dbz5gkn7gaNbptLeXdswqX/8PIkuZAI7W3nZN/zaqz ke8Wdkv/AJ3XQP6YF2FTHKl6PLmqRQTVkLlaQBEP1X7v1syllZvzqJcLVjrGjyaCXAC4 hYfg== X-Gm-Message-State: AJIora9AycfMC4rBKFuafoJf5SadnQwCWB/ZqTYl1Vy66L6XMvx3H9S6 +b4g1o7rWvbhsxn/4nbEf70H4g== X-Google-Smtp-Source: AGRyM1vRF4eRWSTGYdJclCwzuLX1B9QMR649k7jHSPhIkNxAGqz8Oy5U7vy7fCLtbZkUIw7qBrSRUg== X-Received: by 2002:a63:210f:0:b0:40d:dd27:8361 with SMTP id h15-20020a63210f000000b0040ddd278361mr8512615pgh.306.1656607541813; Thu, 30 Jun 2022 09:45:41 -0700 (PDT) Received: from hermes.local (204-195-112-199.wavecable.com. [204.195.112.199]) by smtp.gmail.com with ESMTPSA id s14-20020a17090302ce00b001678a65d75bsm13714843plk.81.2022.06.30.09.45.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 30 Jun 2022 09:45:41 -0700 (PDT) Date: Thu, 30 Jun 2022 09:45:38 -0700 From: Stephen Hemminger To: Shijith Thotton Cc: , , , Olivier Matz Subject: Re: [PATCH] mbuf: add mbuf physical address field to dynamic field Message-ID: <20220630094538.5b27d0c6@hermes.local> In-Reply-To: <57d2ab7fff672716d37ba4078e2e3bb2db126607.1656605763.git.sthotton@marvell.com> References: <57d2ab7fff672716d37ba4078e2e3bb2db126607.1656605763.git.sthotton@marvell.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Thu, 30 Jun 2022 21:55:16 +0530 Shijith Thotton wrote: > If all devices are configured to run in IOVA mode as VA, physical > address field of mbuf (buf_iova) won't be used. In such cases, buf_iova > space is free to use as a dynamic field. So a new dynamic field member > (dynfield2) is added in mbuf structure to make use of that space. > > A new mbuf flag RTE_MBUF_F_DYNFIELD2 is introduced to help identify the > mbuf that can use dynfield2. > > Signed-off-by: Shijith Thotton This seems like a complex and potentially error prone way to do this. What is the use case? How much of a performance gain?