From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by smtp.lore.kernel.org (Postfix) with ESMTP id 29AF8C77B73 for ; Tue, 30 May 2023 03:11:29 +0000 (UTC) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2C61C40F18; Tue, 30 May 2023 05:11:28 +0200 (CEST) Received: from mail-pf1-f181.google.com (mail-pf1-f181.google.com [209.85.210.181]) by mails.dpdk.org (Postfix) with ESMTP id 0C403406BC for ; Tue, 30 May 2023 05:11:27 +0200 (CEST) Received: by mail-pf1-f181.google.com with SMTP id d2e1a72fcca58-64d18d772bdso4567795b3a.3 for ; Mon, 29 May 2023 20:11:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20221208.gappssmtp.com; s=20221208; t=1685416286; x=1688008286; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=SWd1mM5LmQVIy6J2phv+arfp5x0gzNBuPumdxw/N87w=; b=ODkX2SNZjDv3PTO0lrK0B6NNgBw1Iw6gQ8vjF2xe/jVB08kpkAdCFPihV9SXJlgmR3 fwNXO3Va0ndtz/SiOlBTaNn2sOzS38MbevuKOaGCWPg7PqJtUrtrJx1d+gjzYCtwRlaX iFlt3q19tEDG5g+mf6d/3yX4cFH5RcPic62JH9zgJVA90w7WMTp4fIx2oUBXvjW6edQg tsNvnr7fe5i+ST0nXuFKRLpF/EKg/f4KjfN0c28evcSCydj6x+deeMws0Jw/0Ud4EGhq adgv1o238Kgf+tM1VjMNoMgjGP3EwGepZWE7VXHOe5QmgBpt4vSNHdlHITgIh82l2gaa n0ZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685416286; x=1688008286; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=SWd1mM5LmQVIy6J2phv+arfp5x0gzNBuPumdxw/N87w=; b=C0nGtkfr3lXIS9eW5qZBDqnW8uSKmB65CkIXBmISua71gHj7Nf7p6P7DzuPlUvAP5j BZhLKLXArO0hMI7e2nVSFh84iEqHQSsiIlrNPZW6OZKVjrLTayG9leYfXKbox/U2stTS I1KDpIlNyO8Jax1ydYBBbR/bO6AeE1s7CN2xyaot402+mlUKIW7Vc2QhrEzzDHqdjwzJ mn/tldSnFejXSaED7rUtEXONnrrgmbaFJIcyDGuZN5c3qzFzDsHS2KXGcjFeE+yIDkUw W3igRWBB7yQmsUVoO/v2Lutl4yJX81LYDEoJ2b5IFJ6HibiYmi8kYZuAv57Lz27tXN5I IB7g== X-Gm-Message-State: AC+VfDxwlesncyXBwwaROGBKyNt1XtuUNJGxe2WnA3hrGXwXyU5jMYJl H+09zZqTo9ZRJHjg0DNWW2VHsg== X-Google-Smtp-Source: ACHHUZ5EVr0Pl1k5X7ydrZ/uJAkH/9ms8YrVcDX3eB74upM4kdMlRvWDV0tTuCiWQDqWSXi8ofPEZQ== X-Received: by 2002:a17:903:120f:b0:1ab:11c8:777a with SMTP id l15-20020a170903120f00b001ab11c8777amr1136685plh.13.1685416286176; Mon, 29 May 2023 20:11:26 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id m18-20020a170902db1200b001aae64e9b36sm8961952plx.114.2023.05.29.20.11.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 29 May 2023 20:11:26 -0700 (PDT) Date: Mon, 29 May 2023 20:11:24 -0700 From: Stephen Hemminger To: Baruch Even Cc: dpdk-dev Subject: Re: Hugepage migration Message-ID: <20230529201124.55f17784@hermes.local> In-Reply-To: References: 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 Sun, 28 May 2023 23:07:40 +0300 Baruch Even wrote: > Hi, > > We found an issue with newer kernels (5.13+) that are found on newer OSes > (Ubuntu22, Rocky9, Ubuntu20 with kernel 5.15) where a 2M page that was > allocated for DPDK was migrated (moved into another physical page) when a > 1G page was allocated. > > From our reading of the kernel commits this started with commit > ae37c7ff79f1f030e28ec76c46ee032f8fd07607 > mm: make alloc_contig_range handle in-use hugetlb pages > > This caused what looked like memory corruptions to us and cases where the > rings were moved from their physical location and communication was no > longer possible. > > I wanted to ask if anyone else hit this issue and what mitigations are > available? > > We are currently looking at using a kernel driver to pin the pages but I > expect that this issue will affect others and that a more general approach > is needed. > > Thanks, > Baruch Report this to upstream kernel regressions, they probably care about it. Doing a kernel driver hack is overkill, maintenance and long term technical debt problem.