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 5CF6E43895; Thu, 11 Jan 2024 18:00:17 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EC640402AD; Thu, 11 Jan 2024 18:00:16 +0100 (CET) Received: from mail-pg1-f182.google.com (mail-pg1-f182.google.com [209.85.215.182]) by mails.dpdk.org (Postfix) with ESMTP id 209F640269 for ; Thu, 11 Jan 2024 18:00:16 +0100 (CET) Received: by mail-pg1-f182.google.com with SMTP id 41be03b00d2f7-5c6ce4dffb5so2504097a12.0 for ; Thu, 11 Jan 2024 09:00:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1704992415; x=1705597215; 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=Of1jj26obtG5jPZns7MEawcPJL1Ll7Ik7yfE0XlfgRA=; b=1tOTIW699/oydXLWsyNvuWF9zyQSOvLW8uIYKqnp018GoTYlG3v9cbQw6coAzb23Xh Ji5A53HCu+dVbnR/WxIzLqlB0alyI2+dzZhX9W3XW0PhtnSOFkMuULUSNISil0Q+TEex oxeXlVqTe6Bg42pcutW6zFDsTgXsBJQCoMiyG0lUO+J0mNm5n5G+FTu311sWBm+uWVqB tZkeynPp4VW0sqBnTLnIOLfQ3sBRtZs60hE4ZvZlTod25/7rPDF/ZamGphD8PQ7sGgo+ YdM2D8A/7jo4dgUqjehxOLmu7jSfhbpHh0pythl1ZpbeEa3nqjk73BDOnbKmo41u1gGP tnpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704992415; x=1705597215; 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=Of1jj26obtG5jPZns7MEawcPJL1Ll7Ik7yfE0XlfgRA=; b=uISpKw2Wh/UNAvoiCH6PXelrzK4wHb6DVqF3Q0azyHHqzCNMhZRUWstmf5tXBW+wJ4 4UtkQD48mOelUf9xT6Oe1YjFj3DgzIb4MBSdEZyK84mJcN+On3OAcsDs3Ij6d7vfPn6x FzPAf/YdvCQCCUN7RN0in3rT5xVs726CbgrYfbInHDskdEPSTZa2I87gqO/wQOxVGsZK r7lv9iUXGZ6PAjsMkUMFx/D8wUDXbmWCef7+3vzHvCBLlDnPulCcTM2ZxNxlH+whKg1/ +sM7TCEjjcrUR1jXqMowmbRfTlG6mCiYSu3bw+UOJ66LM9fsvu88IGFdV5sGsZmIYlJ8 OLOA== X-Gm-Message-State: AOJu0YxcCyJ6Ap7+uRfFQBugb1t79GpwkwZc0CI2gMyz+fdHfUSMvvWQ Q65ayyXiR/bg40zcoSWcp9EJIXpvzwIcgg== X-Google-Smtp-Source: AGHT+IEUvA9aWzq+myWR+3EaNxiRk3M5LGEG2wh4TYZq7ijy9eT5jsZr/48ADWHj9FhgJUpFgpN0cA== X-Received: by 2002:a05:6a20:5486:b0:196:d90:aa62 with SMTP id i6-20020a056a20548600b001960d90aa62mr126812pzk.121.1704992415016; Thu, 11 Jan 2024 09:00:15 -0800 (PST) Received: from hermes.local (204-195-123-141.wavecable.com. [204.195.123.141]) by smtp.gmail.com with ESMTPSA id i24-20020aa78b58000000b006d99d986624sm1399058pfd.151.2024.01.11.09.00.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 11 Jan 2024 09:00:14 -0800 (PST) Date: Thu, 11 Jan 2024 09:00:11 -0800 From: Stephen Hemminger To: Cc: , Thomas Monjalon , Ferruh Yigit , Andrew Rybchenko , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , Subject: Re: [dpdk-dev] [v1] ethdev: support Tx queue used count Message-ID: <20240111090011.664c8888@hermes.local> In-Reply-To: <20240111151745.3800170-1-jerinj@marvell.com> References: <20231219172948.3909749-1-jerinj@marvell.com> <20240111151745.3800170-1-jerinj@marvell.com> 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 Thu, 11 Jan 2024 20:47:44 +0530 wrote: > From: Jerin Jacob > > Introduce a new API to retrieve the number of used descriptors > in a Tx queue. Applications can leverage this API in the fast path to > inspect the Tx queue occupancy and take appropriate actions based on the > available free descriptors. > > A notable use case could be implementing Random Early Discard (RED) > in software based on Tx queue occupancy. > > Signed-off-by: Jerin Jacob Has anyone investigated implementing dynamic tx queue limits like Linux BQL?