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 64FDFA0032 for ; Tue, 12 Jul 2022 10:32:37 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EF67141109; Tue, 12 Jul 2022 10:32:36 +0200 (CEST) Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) by mails.dpdk.org (Postfix) with ESMTP id 254E5410EF for ; Tue, 12 Jul 2022 10:32:36 +0200 (CEST) Received: by mail-lj1-f180.google.com with SMTP id u14so9049914ljh.2 for ; Tue, 12 Jul 2022 01:32:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=rzjJRbExLc4UCD8NWuZNPLFA8FLVG08u0fKJGKrZ1m4=; b=kk5KnNnh/mRXf+ROWTmWOBuGmrHFTGwFR4CztgzodB91NAzc4hzRdn7p3GTxRZxVz3 bzNp11z5Ltc2hChPahEfFiM5jxLS9LRJgTPdZyreqTHvu2Ojjldo4p7k/5ZiWCySyEMk QwvpGQ+tcGu+8lOhhEGqOY7SaOzWPRHZZ11PvM87nQHPVjxjsLKMDhwXUkAul5V2tiKV OYPwY6Z/ZoK14OFlymAC8ZrGeIN2L0+2kdW9IjuIFn5r0fLMfAqdmmLZk5RUxtMocEAb dFMXLpR33LG5jC/LwoLyOWxXICaZV6RSJXP22R7a3lw/xDArGv8WrjYBFf4LEbLHJYuA YVBA== 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=rzjJRbExLc4UCD8NWuZNPLFA8FLVG08u0fKJGKrZ1m4=; b=fTyNP0vAPjNsQvwafVEp1Fap1lBypUBh7kWJFZ8T88qECwv1ofzB2HFsaXXxdWc+HK 7ceXKPuhthP369MCClpcEfIBiGYa1ocNtdxkjUGADS67FMUnERAQzI3mbMrhZLnUpHAo jejRF9AqKVObhIlAkdOlH2kqIBiQg7ps7nk5rDtBo9gBGC7XoKvnbzA4avVtNlQqrB9Y 27ahvhiVhWN5Mca9nsb6UHPaMbwYkhWG6Yqg+CQ6eO073LMGKm/m/xMiTJ9HdyJWbprw 5N++1QeLhovUzVV3VR8gEgdcZLmLtyWvvKFXpgDEpv0c7H/VrAJ1dgB1C1pY8N+jN66O ckMg== X-Gm-Message-State: AJIora92rAG57UG/7qkD2I3hGGvhpJ8AOUQd3jNuEueoSmkXxdCC6+P5 eLtZtb7FXREsCHUn/2b+iy4= X-Google-Smtp-Source: AGRyM1snwiBGgfwltkyHZ7Km+d+D/OKYofQpkFFlt3/hpFV84hpRv+8LBU9X81LbHUdaVTBUrzXWlA== X-Received: by 2002:a05:651c:160a:b0:25a:62a4:9085 with SMTP id f10-20020a05651c160a00b0025a62a49085mr12158071ljq.214.1657614755576; Tue, 12 Jul 2022 01:32:35 -0700 (PDT) Received: from sovereign (broadband-37-110-65-23.ip.moscow.rt.ru. [37.110.65.23]) by smtp.gmail.com with ESMTPSA id y16-20020a05651c107000b002554dce4048sm2301665ljm.53.2022.07.12.01.32.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Jul 2022 01:32:35 -0700 (PDT) Date: Tue, 12 Jul 2022 11:32:34 +0300 From: Dmitry Kozlyuk To: Antonio Di Bacco Cc: users@dpdk.org Subject: Re: Getting mbuf pointer from buf_addr pointer Message-ID: <20220712113234.1209dd36@sovereign> In-Reply-To: References: X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org 2022-07-11 11:21 (UTC+0200), Antonio Di Bacco: > Is there any API that allows me to get the MBUF pointer given its > buf_addr pointer? No. How did you come across this need? Sounds like an app design flaw. What is the original problem you're solving? P.S. It may be possible in specific cases when you know (from code) how mempool sets buf_addr for a given mbuf, and that PMDs don't change buf_addr with the used set of offloads. Apparently, this approach would be extremely brittle and dangerous.