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 171B2466B3 for ; Mon, 5 May 2025 14:53:11 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 77B8740E35; Mon, 5 May 2025 14:51:59 +0200 (CEST) Received: from mail-wr1-f65.google.com (mail-wr1-f65.google.com [209.85.221.65]) by mails.dpdk.org (Postfix) with ESMTP id 7FF6740151 for ; Mon, 21 Apr 2025 04:16:35 +0200 (CEST) Received: by mail-wr1-f65.google.com with SMTP id ffacd0b85a97d-3995ff6b066so1840897f8f.3 for ; Sun, 20 Apr 2025 19:16:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1745201794; x=1745806594; darn=dpdk.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=66iTbewpXjNxc76uGOEvmyX9AN4c6TzMhs6VIH/Fy+o=; b=BnpvRp5/XZbQVaq3kijouSQfnVhRu+959Dm7xIpHyXl+Cbt6cVeREmaruN/aovNDzE 6U6WYR+lpScYwSJUWc66dD/Gag5qZs8aG+ov4QKDAKr89dgfIrycFYG+4ptmdF0PxseQ mosjKB/XaYELg1MMyN1MSvI0RecZW89jO0TQN5hdKYFYcskrhhhpM5c1KhuY+9nOG0oU 9DfBY4Cg1cxhEdL86lJPvNXWJaOtW43PS9wYRmpVQKzFabgxJ2OTzZyBTXrP/6XY7noz XKoDMAFoHTSQTOI9xUV+5gkRBDi1kIrvujtIft1pdgVYRvboLAMz2S56bvbcdafmzZgt VwMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1745201794; x=1745806594; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=66iTbewpXjNxc76uGOEvmyX9AN4c6TzMhs6VIH/Fy+o=; b=DR7ivxi/MJMIVoKXz1KGqj4zpOc7wUkN5dpFTx3lFpSfH4XkSzdetaWTVGmHyKa2Md 4WDe4bjqePaxFSdC8RRxBJJU1aM3iR6iRw3312f7B0p9My3KEJpx/0lb470xw4x8mfQq qdFpm0qq2z24JMoh49/tpF+RftB1TDFOdzeTEybdDdTHxMbWKs1ywrgzNp6ip1wojPXp e+03bkgCg/qRLRPLGqu+JvbXo6jPOnSZ5Hyd/pBOgCpCOcf9VwC2GnL2W4B0Pqu9fP6l gSumHhvqSMAKd4rlYyrxC7WlHNioiZr2cd3U9Q77z0SYTxCUthQudBdx4ubLOjIb8rtj TsEw== X-Gm-Message-State: AOJu0YyCpwlx136xdjXA4VCaa2awzgmJPsmx6XvinzgtBXj98BMojUyU IBRaRdvRKXzQP8GT+Ijg0L7N61UUCHJwyjzK1W9IUkjaMa0tFGwr/OOuTKdpIOsD5EWZYBn2PT2 32jjj3pwi7SgMqr6X0kF6upYcRNirT/qXZM038A== X-Gm-Gg: ASbGncuurRwNjMV+djlCBjI08CUttF0sW0PnflUQZFjjwb3rU8nMaYZJSQ2izcZDpps csy4agBDEfFxmHtNcEJduifX8oStllfSVQ3S70QuM07ocKKEHuI4lBlvDHcuA/Lwh08jyXm203l PaWSIgarAMQ/Z1rYa/LrxKLwnG X-Google-Smtp-Source: AGHT+IHJ8kwMXfathvN4WqVBCR7++iyw6qzjVAUn6CU3iZ9HXb61CIWGlhUZOXD0gYCgugEg05KMZget+PletlmopFw= X-Received: by 2002:a5d:5f8a:0:b0:39c:30d8:f104 with SMTP id ffacd0b85a97d-39efba39999mr6323228f8f.6.1745201794286; Sun, 20 Apr 2025 19:16:34 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?B?5q615LiW5Y2a?= Date: Mon, 21 Apr 2025 10:16:23 +0800 X-Gm-Features: ATxdqUHo8DEXgAKQj7kbFJiAglljvhfcmkQEEotdt0OpS6su208wafv-g1A3-Hs Message-ID: Subject: Use external_buffer by ret_pktmbuf_attach on dpaa2 device To: users@dpdk.org Content-Type: multipart/alternative; boundary="000000000000028be60633407586" X-Mailman-Approved-At: Mon, 05 May 2025 14:51:58 +0200 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 --000000000000028be60633407586 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello everyone, we want to use external_buffer on the dpaa2 nic, but when I use rte_pktmbuf_attach, the network card cannot read the content of external_buffer correctly. When I map this external_buffer through rte_fslmc_vfio_mem_dmamap (an internal function), the network card can read the data normally, but I don=E2=80=99t know if there is a problem with this= use (some restrictions that are not considered?). If this use is legal, I hope that developers can add dma_map and dma_unmap functions in rte_fslmc_bus, so that memory mapping can be completed by calling rte_dev_dma_map. Thank you very much. --000000000000028be60633407586 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello everyone, we want to use external_buffer on the dpaa= 2 nic, but when I use rte_pktmbuf_attach, the network card cannot read the = content of external_buffer correctly. When I map this external_buffer throu= gh rte_fslmc_vfio_mem_dmamap (an internal function), the network card can r= ead the data normally, but I don=E2=80=99t know if there is a problem with = this use (some restrictions that are not considered?). If this use is legal= , I hope that developers can add dma_map and dma_unmap functions in rte_fsl= mc_bus, so that memory mapping can be completed by calling rte_dev_dma_map.= Thank you very much.
--000000000000028be60633407586--