From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <users-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 78B8146192 for <public@inbox.dpdk.org>; Wed, 5 Feb 2025 00:31:20 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0BDF84021E; Wed, 5 Feb 2025 00:31:20 +0100 (CET) Received: from mail-oo1-f45.google.com (mail-oo1-f45.google.com [209.85.161.45]) by mails.dpdk.org (Postfix) with ESMTP id 08043400EF for <users@dpdk.org>; Wed, 5 Feb 2025 00:31:18 +0100 (CET) Received: by mail-oo1-f45.google.com with SMTP id 006d021491bc7-5fc447b03f2so180921eaf.0 for <users@dpdk.org>; Tue, 04 Feb 2025 15:31:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738711877; x=1739316677; 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=NhBp5r63L+X/bhR9s21g4NzvUU0/R4u8fWVtsQT2E8g=; b=YLEA79YwYqF25B+qIiWShmw4ymI9cRXCqP7tm9jaAAUziudD9nT8wfjpv0a9ubj8LR M5z3cfzASFAHV0FhXo7ggLt4PSMt0DB3Xxbv7JBSevzaBfoAfFds9uOk7Ws+aMoInwZP ejgnqVWxPg7ePhloTbacheXRo66fJE0PLXe2+9nitznYuhwXcBE5DpLSn5qr3YhAhUBW OMK/o4pkOaQoWAHGa3QgOucHPN1BtqdJh+eJB0NosnLqvk+M0MO9eW5MBx9hB0RN1GEC iPEHB4J5NLQ7N+F7LjepyrvOfEeP1e0oLesr6QK0bhuvYQELd/CluMng9pYbduwxQuN/ 0EUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738711877; x=1739316677; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=NhBp5r63L+X/bhR9s21g4NzvUU0/R4u8fWVtsQT2E8g=; b=lumkKhRA591glY7nF6WzlcEUdjiObGaTQ6aqNUsxdgLvadX0spAORg3BtQZcbTdLED Y8RLmbvEe6FjwDhmJysiEteUUpka+sQGhMhqcumKN4BGKOPdVMPy5nPVxcvMeLNO0bxR BqfD/HTCu2RyT+wVCejkJG9jcG5gG1E4rQm85uYdpRHq2rx5yDTdGBwO4KiSAkYmPijM BhKsxfQC7J2cYx07t9T/OWVSGr6aJYFnirksgyWR9XXYm1csQ1HDviSzzncAucVS81iF /9+2N4c0pI/HMT2OoImMp6ks97aP5z5H2en5/OM47BSPx3phtWpfnLlMA+HWTwuQc4Tu 56bw== X-Gm-Message-State: AOJu0YzkH0QwybMmdGTPBlCRVhK8al5nepiQcZwgOV5zyKI6G5PUSpes /l9y767K9nXr5x8Co6dhoA/3jJNgGV5WYfOSSyoixO6WoLdhRRFcsnQ0ggAPC9g216UCoeRBejQ Q+g5H/Wu17lSn8V6JchvmHEER/HJ/2g== X-Gm-Gg: ASbGncsAo37+AaOB6k15LZIu5qMA63FNoFbzjjCO+s78Ey0boR79MSg522CekZSk8nu UZqNsdQtfSxCM9D+//sElK/nCi66RoGLio3t3C8oQz38kBUgbv2xlST9tzr2mWDX3PuGglCM= X-Google-Smtp-Source: AGHT+IHaW4fcAbFegdJNERdzOJa+uyeuMp7t3hneBKkxLjS+cxoy4waJgLCL0DHovbEEqxhbITc3PyjtWN+FdEssThk= X-Received: by 2002:a05:6871:5829:b0:29f:f1cc:12a5 with SMTP id 586e51a60fabf-2b8051336admr554231fac.31.1738711876943; Tue, 04 Feb 2025 15:31:16 -0800 (PST) MIME-Version: 1.0 References: <CANTAOdy7sNDDHDgL_Ow7xBJWeYEgbbik7Ab7x4wm0uFmgzFsXQ@mail.gmail.com> <20250204152635.19deced0@hermes.local> In-Reply-To: <20250204152635.19deced0@hermes.local> From: Alan Beadle <ab.beadle@gmail.com> Date: Tue, 4 Feb 2025 18:31:06 -0500 X-Gm-Features: AWEUYZkfrQ499LbfVc2Q6P0zIdwIKnXjQ0ayEQFkX90mA0mXEEVvMLZDhghEKaU Message-ID: <CANTAOdxZHKuYisWBjOLL_uu6OxDuzqY=C_q_XcspOuZ7Y6asTg@mail.gmail.com> Subject: Re: Corrupted payload when sending many individual mbufs in loop To: Stephen Hemminger <stephen@networkplumber.org> Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions <users.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/users>, <mailto:users-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/users/> List-Post: <mailto:users@dpdk.org> List-Help: <mailto:users-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/users>, <mailto:users-request@dpdk.org?subject=subscribe> Errors-To: users-bounces@dpdk.org > Are you using refcounting of the mbuf. Are you reusing the data? > DPDK has no callback or mechanism to indicate when data has actually been > sent; ie the mbuf may still be in use for some amount of time while sitting > in the device transmit queue and being DMA'd. Fragmenting can be complex > to do. Unlike my earlier threads, in this case I am not saving any mbufs nor am I doing anything at all with the refcount. For retries I am regenerating the lost packet from scratch each time. The problem is that at high tx rates the payload is getting corrupted and I have no idea why.