From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9491CA2F6B for ; Tue, 8 Oct 2019 23:35:21 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DC3FC1C198; Tue, 8 Oct 2019 23:35:20 +0200 (CEST) Received: from mail-wm1-f45.google.com (mail-wm1-f45.google.com [209.85.128.45]) by dpdk.org (Postfix) with ESMTP id 4E4E41C195 for ; Tue, 8 Oct 2019 23:35:19 +0200 (CEST) Received: by mail-wm1-f45.google.com with SMTP id a6so4724016wma.5 for ; Tue, 08 Oct 2019 14:35:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=oDL4AoOkHGPnhOQU2wWZRrUd0ATxJjLF96Z7G6DnBKA=; b=iF1zou5rI6Pi6oKgVYnSvhtf2IBd72rwfzIPD5UjOFzL+xuUOW8183Ruhwd6jAq30T y4mn2zZ6SdM7wiOhxOCRDeHYzqZGs67IpoOd3+ggwmac27507Fbt2DteopV8Nn0EMMbi 0AzcD7vdXPr33lCNRJLc2jxlrWreRgrkq5qyFG1rh7iugrOg3WHVtsOiPaSWj1R7idM2 GKLWuR2/eoIbFyg0Q9Oo4+XZXIK2kdh2QJ1UKfiVCIR/G6IgGEAux4aFMcg765qbwIIy j4L/t5124MuAM2hvQZOjJkXEH2xS4h1ae+QZARC08ipoX0H+VPLiCjpQtPJbtpd2OwI8 GFxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oDL4AoOkHGPnhOQU2wWZRrUd0ATxJjLF96Z7G6DnBKA=; b=sGh0+vW4vfuIjOHgdvbPiUFVwrHg/SQaN3pbq4cKQ/BnuaThBmmB0ZHetl8SObDBEp Hdb1z+MwEE3Pt+6f4dWZQSel6ew3W7py+x5BByRl+rstjo6Qh6pfcgiuBEHiKjpzFeNk gTr20AvBPN6XL5kzhTgTxICdCSmjMzpIAIgzBW3fdweaz5LZzbDbddU0xaVqvFYqIaT0 P2BMSKR/fVzRNECJ/VyAXgZnfUfnt9HJ1wM1/m4lBfA/24vHjCV6XKzoEWH2hgJt8Lyl Pj9Cz/owOQr0tmGzBRByD5JU/UvOuM3ubPShqoehPv0QR1+9Vl3iDG0ScivubTCvgTOB QrQg== X-Gm-Message-State: APjAAAVc3ajfmeT4bws0DCbaAACRH0LAqd+gT6OsEbooj/fvmYSCH2/D lgVZbAmT77Mx9j1e6d3PYU9Vtc95pE3VRkw417cbneOSc4o= X-Google-Smtp-Source: APXvYqwGLX31nlYOdRPac7OnrrQbCx/6/mTTGYXYUaAKe3JUuPHT6msCFSpD1ouDwNwOHk/PFKtkLSNFtEE3JHTBCGU= X-Received: by 2002:a1c:7418:: with SMTP id p24mr160990wmc.132.1570570518582; Tue, 08 Oct 2019 14:35:18 -0700 (PDT) MIME-Version: 1.0 From: Cliff Burdick Date: Tue, 8 Oct 2019 14:35:07 -0700 Message-ID: To: users Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Transmit Chained Buffers On mlx5 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi, I'm trying to figure out how to transmit a chained buffer, and I can't find any examples or threads on this mailing list to do so. My assumptions are: 1) Only the first mbuf contains the Ethernet and other packet headers, and all the rest are essentially just appended to the end of that. 2) Once transmitted, the driver will construct all links of the chain into a single jumboframe. 3) DEV_TX_OFFLOAD_MULTI_SEGS must be set in the TX offloads. After setting up everything as above, I construct a chain of buffers using rte_pktmbuf_chain. When I call rte_eth_tx_burst, it reports 1 packet sent for the first packet with 2 segments, then 0 packets sent with packets containing 20+ segments. Is there some limitation with chaining that I'm hitting? It seems the maximum number of chains is set to UINT16_MAX in DPDK, so 20 should be plenty small. I'm using ConnectX-5/mlx with DPDK 19.05. Thanks!