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 B397A48BA6 for ; Tue, 25 Nov 2025 09:06:52 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 46A75406B6; Tue, 25 Nov 2025 09:06:52 +0100 (CET) Received: from mail-pj1-f48.google.com (mail-pj1-f48.google.com [209.85.216.48]) by mails.dpdk.org (Postfix) with ESMTP id 6D55C40267 for ; Fri, 21 Nov 2025 15:17:57 +0100 (CET) Received: by mail-pj1-f48.google.com with SMTP id 98e67ed59e1d1-3436cbb723fso1721220a91.2 for ; Fri, 21 Nov 2025 06:17:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1763734676; x=1764339476; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TS93xc2rn3pvMdE3pTBrapZ7fwdxrCGTWkdHLxP/3CU=; b=fSfZKYhMxCQLMiu2C9Y265OstiFAfGoSDdo8ZSrhcPLYexYdb1+Mw48odES6Kjf+o1 9l1Xm8cELqRTOIkhPqsH2SifINqE0SK5iCrBl0XAg9iUmYSxqsLyUCepBnOlnJGVFwyz uOXNLYOPWGiMobVwkWgS2VQg1A09B0Ow3AhXkVl88LOXk+Zo3OiG9IwS1TrctNbvm8+v kUwYJRsJKgqJQqTTACYiBcco/u96lqxWYj9lWvXKFF5lDyq+JNZBnl31FYIEMVAsXTfM FPYUOGrktJmYFi+iTE02YezwFcGT6bYyOOqXlmHPZgF1Ft5ulgvTzMQtp8UvZtP+humr ncBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763734676; x=1764339476; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=TS93xc2rn3pvMdE3pTBrapZ7fwdxrCGTWkdHLxP/3CU=; b=pOB9gppVNpeLuUJcYQcz/oPgk8viuImad20uc2L2vGRaM3PGVG3dqtJ+N66fgVErJj e3o2W3MrAMG+LdFvZ4OUJqft9RtXwv58rRzz9PeuTEBcZ+E2gJ39NgRRHuVO95l23i4T 6qiqwXLGz0ubsnkwkYZ+qANgdMxobo/KahcH0WoS91v74iz6PMR1cQiCxn6iOneAVWWo qWtv4Gnzg+RzQ7UrS10VsKUz6tQdSHBywMseio1bspbG4OGnpQjlJ+94F7Uj1qkDF2P8 kkA2MzzQERsVIEVOGBzyhAoAYWQb3EqOLI/04ut2pZDOcTgPeK9eGNmsMv//BEh8f+OF R7FQ== X-Gm-Message-State: AOJu0YwCUyrJnY1sYaI1xsAp73B2+ZJUc++QLLKQer71vRYiPbavUpQ9 cINYLK0XjwnvTiPIFhD2PZSJgMcuRE0k/hn+CJaW3XObfoG0m/GYgCunO10vP1SsSWa3bpdXxpk clmhofSvVhxeQug50ZNpvUYcOtfTF3Yeu0Mi+ X-Gm-Gg: ASbGncuLFqyAGpnnaML2efDvUhr8ivJBfERom/k6Sx9zdskI5A3G6iclAih3s+vHbzU SSjPtwNKO7Pz0jcnZ+4ChjCTMY0e/CI5VB6IaEAsIK/+IMerFkeG9PCp/Ihh6xPHYlEgRcTdH+N i1d/heblUVGsbKfK2M69biHHKHtSKyJUj2qMnu95uPbqJg7SUXd1KHfoxfWX8bXjM/ZnFKIaUHO xOUAEhWzqIvv3CHH+SBoSAZze9WCq3v6IInfFYC1DX4SIi3mQLI0Y2yXicOwfa9TWT3U5ue X-Google-Smtp-Source: AGHT+IFLuq8SgRLvTniyMbhRJOq2y3YyDKnceNWOfP0pqwmtSVSswSG3Y8RYDTmE2Z9kix9tWTy4GZC8UAgYF+Fq3Gk= X-Received: by 2002:a17:90b:350b:b0:32e:6fae:ba52 with SMTP id 98e67ed59e1d1-34733e436eamr2944234a91.6.1763734676199; Fri, 21 Nov 2025 06:17:56 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Wan Bingbing Date: Fri, 21 Nov 2025 22:17:44 +0800 X-Gm-Features: AWmQ_blTekgQ8aVKyCXh6YbixlF3D2K540qKgAaEvjgNLMT6dc11VDzzvZaYtPw Message-ID: Subject: Fwd: Question: PMD behaviour without hugepages in DPDK 23.07 (XDP PMD in Kubernetes) To: users@dpdk.org Cc: "chenxiemin@gmail.com" Content-Type: multipart/alternative; boundary="000000000000da5d5706441b7ac8" X-Mailman-Approved-At: Tue, 25 Nov 2025 09:06:51 +0100 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 --000000000000da5d5706441b7ac8 Content-Type: text/plain; charset="UTF-8" ---------- Forwarded message --------- From: Wan Bingbing Date: Fri, 21 Nov 2025 at 22:15 Subject: Question: PMD behaviour without hugepages in DPDK 23.07 (XDP PMD in Kubernetes) To: Cc: chenxiemin@gmail.com Dear DPDK team, We are currently deploying an application utilizing Seastar and DPDK (version 23.07) with the XDP PMD inside a Kubernetes environment. Due to infrastructure restrictions, we cannot allocate hugepages on the Kubernetes nodes. In this environment, DPDK fails to initialize the XDP PMD because hugepage-backed memory cannot be created. Although the EAL is not started with the --no-huge parameter, no hugepages are available to DPDK, preventing the PMD from sending or receiving packets. We are aware of the known issue documented in the DPDK release notes ("PMD does not work with --no-huge EAL command line parameter"), which explains that PMDs rely on hugepage-backed memory because DPDK does not store the necessary physical/IOVA information for memory allocated via malloc/mmap. Given this dependency, we have the following questions: 1. Is there a currently supported method to run a hardware PMD (specifically the XDP PMD) without hugepages, or is hugepage-backed memory strictly required for all hardware PMDs? 2. Are there any ongoing efforts or future plans to support PMD operation in a non-hugepage mode? 3. If this limitation is architectural and not planned to be addressed, could you please confirm this? This confirmation would allow us to evaluate alternative approaches, such as using AF_XDP without DPDK or relying on the Seastar native stack. Any guidance or recommendations from the maintainers on how to proceed would be greatly appreciated. Thank you for your time. Best regards, Wan Bingbing --000000000000da5d5706441b7ac8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


<= div dir=3D"ltr" class=3D"gmail_attr">---------- Forwarded message ---------=
From: Wan Bingbing <wantmac.bingbing91@gmail.com>
Date: Fri, 21 Nov 2025 at 2= 2:15
Subject: Question: PMD behaviour without hugepages in DPDK 23.07 (X= DP PMD in Kubernetes)
To: <dev@dpdk.= org>
Cc: chenxiemin@gmail= .com <chenxiemin@gmail.com>


Dear DPDK team,
We are currently deploying an application utilizing Seastar and= DPDK (version 23.07) with the XDP PMD inside a Kubernetes environment. Due= to infrastructure restrictions, we cannot allocate hugepages on the Kubern= etes nodes.

In this environment, DPDK fails to ini= tialize the XDP PMD because hugepage-backed memory cannot be created. Altho= ugh the EAL is not started with the --no-huge parameter, no hugepages are a= vailable to DPDK, preventing the PMD from sending or receiving packets.

We are aware of the known issue documented in the DPD= K release notes ("PMD does not work with --no-huge EAL command line pa= rameter"), which explains that PMDs rely on hugepage-backed memory bec= ause DPDK does not store the necessary physical/IOVA information for memory= allocated via malloc/mmap.

Given this dependency,= we have the following questions:

1. Is there a c= urrently supported method to run a hardware PMD (specifically the XDP PMD) = without hugepages, or is hugepage-backed memory strictly required for all h= ardware PMDs?
2. Are there any ongoing efforts or future plans t= o support PMD operation in a non-hugepage mode?
3. If this limit= ation is architectural and not planned to be addressed, could you please co= nfirm this? This confirmation would allow us to evaluate alternative approa= ches, such as using AF_XDP without DPDK or relying on the Seastar native st= ack.

Any guidance or recommendations from the main= tainers on how to proceed would be greatly appreciated.

Thank you for your time.

Best regards,
=
Wan Bingbing
--000000000000da5d5706441b7ac8--