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 E54D545A9A for ; Thu, 3 Oct 2024 10:34:41 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B6CD14025E; Thu, 3 Oct 2024 10:34:41 +0200 (CEST) Received: from mail-lf1-f44.google.com (mail-lf1-f44.google.com [209.85.167.44]) by mails.dpdk.org (Postfix) with ESMTP id B0A6E400D7 for ; Thu, 3 Oct 2024 10:34:39 +0200 (CEST) Received: by mail-lf1-f44.google.com with SMTP id 2adb3069b0e04-5398fb1a871so637653e87.3 for ; Thu, 03 Oct 2024 01:34:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727944479; x=1728549279; darn=dpdk.org; 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=KOcnJtu9NDmbqOCsPbgK5Ss49rcIrKhlhsmHTuVaVQk=; b=D0F8xYgHcGvT6PntBQ16j7Le5c+ufKfb5mhOitjlH5G4D4zo7aaTjYtkzq4tLZmi3m 8FznMnMUU8rtUtEvKqupjt44uGJtjw2DSl39eZRMm0XYa6q4qpS3JI2JANr4JUQBE75m zVlH62OnKslm5dswD94j1FzU4Ug0fbQlKOYny3XQR1miAI8jqD+HiDJu+rqIsUWgv1Wc +UNVovROzjcr/Y/ahRcrJ93J6zK2gp9YtwMhnP/yWEY/8p2gQI7nsjjYOP6k6e+AZ5bm mH1d86Ctv8LVp/pwFSjbLhtiTl3LsEQG32HiaAWDEaO65GzYb0x/qOIrWgWn/43IePiO puNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727944479; x=1728549279; 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=KOcnJtu9NDmbqOCsPbgK5Ss49rcIrKhlhsmHTuVaVQk=; b=QJVcGq3QyndPGl9N8BCT3TqdijYXb8fuzgmwzmJSd3mCumnHXk6L4HwGDZ+hJAyZ4l 5lGWYqRRsZN2caaZTqXRvHa55lGeeDShgh5tbtaZ/KQ9N75nXJI2ob+UoRxc3D5+c6dv De0ZwH6/9J2rhR1dlEnTqYi93RFqXzcgfw9rskgwZufBAViiJMo+G78CtK2AiW9ICFnl LFuW/zJq/AsyzOEfHTqkN3v+i6VRZLwCC3GQRlg/eHkPxaDZOXKQZn5xVB0xvzm5RsZI 9NwkPhoWFiIPIoocZZR3hvg+9oGUywQhr4bLS7viktgqnKllRF4KniXP8Y6O7dw8e6om cpUg== X-Forwarded-Encrypted: i=1; AJvYcCUtelVBDAY+6mej/EsYOOtwVXGeyspKH1lJLzom/6RWdTmxpZu7nWFkqPZQUiRlU+s335szQQ==@dpdk.org X-Gm-Message-State: AOJu0YyMpz1HNBItGodA3T2l5fFtxFk4DZztRdFtAo/h7tFfaQ7MUGh4 YGmwGMRvnztGpjgln+9C7GZ7VansiKFsq5JNFlvzNvEWD62RLeXe X-Google-Smtp-Source: AGHT+IH9XLngdnzWaHRLu3Sp2K9Qb5JTgIfOk8YIV2ef1cJrMWPU0mUWkcdV+nowVfZnko2vyy55HQ== X-Received: by 2002:a05:6512:138c:b0:52f:d15f:d46b with SMTP id 2adb3069b0e04-539a0660e90mr3575323e87.14.1727944478624; Thu, 03 Oct 2024 01:34:38 -0700 (PDT) Received: from sovereign (broadband-109-173-43-194.ip.moscow.rt.ru. [109.173.43.194]) by smtp.gmail.com with ESMTPSA id 2adb3069b0e04-539a8256c18sm120439e87.105.2024.10.03.01.34.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 03 Oct 2024 01:34:37 -0700 (PDT) Date: Thu, 3 Oct 2024 11:34:36 +0300 From: Dmitry Kozlyuk To: Mikael R Carlsson Cc: "Pathak, Pravin" , Stephen Hemminger , "users@dpdk.org" Subject: Re: Relation between DPDK queue and descriptors Message-ID: <20241003113436.2dc280e7@sovereign> In-Reply-To: References: <20241002082918.0207a447@hermes.local> X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 2024-10-03 07:37 (UTC+0000), Mikael R Carlsson: > Hi! > > Thanks. > > According to chatgpt the descriptors are shared over all TX queues. > > So, in a 4 TX queue and 1024 descriptors scenario I would be able to get maximum 256 descriptors per TX queue (If I want same amount on all queues). But if I only used 1 TX queue, I would get all 1024 descriptors on that single TX queue. This is not so, ChatGPT errs. The number of advertised and configured descriptors is per queue (the latter is per the specific queue being configured, actually). You won't get more descriptors per queue if you use fewer queues. Note, however, that queues consume NIC resources and larger queues stress CPU cache, so it is not always the best to have many queues or large queues.