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 DFC90437B4; Thu, 28 Dec 2023 18:17:02 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5F110402C4; Thu, 28 Dec 2023 18:17:02 +0100 (CET) Received: from mail-pl1-f176.google.com (mail-pl1-f176.google.com [209.85.214.176]) by mails.dpdk.org (Postfix) with ESMTP id 18FB1402BA for ; Thu, 28 Dec 2023 18:17:00 +0100 (CET) Received: by mail-pl1-f176.google.com with SMTP id d9443c01a7336-1d3dee5f534so47619635ad.1 for ; Thu, 28 Dec 2023 09:17:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1703783820; x=1704388620; 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=hmptfTqFimFORljgaoA//29aYCPyySGTb9/fWW2QKcY=; b=2JkESTXcm/pqqcjAF4eKDK4WnfqTytlwsxg544MM5bfv3WQ5LL1dIDsXUghpMjU9T9 7wwNolqxllYE6Dy+ZIIs6wW5h8TlY6VOrhmvUBkeRDbWVVD3wNTtnD5W/bxuQN/sgy07 tzN9RitBzweWwLMhO0AEObOn/qZfUNiFnXUquXJrbDDbBgMEo6RFexZ9qBHnFrciHee2 m07rTRhapBaldcyWcG3awG50LBoMjGK50LxqU8H8ZMtdgr109QXU/+1atAAb7RGIJw+k Nd1EGOrxISavPsKj4hJsbW7R7aKeiYAk54aNqva6hTfeogvjdYXI8dbWcS9oMHo/SWr8 CTSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703783820; x=1704388620; 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=hmptfTqFimFORljgaoA//29aYCPyySGTb9/fWW2QKcY=; b=imH2ydrdoXgXQGwSLEzf8Vui/peS0Rn518Rzwc9WDN6byfqz0dVOTtgJ5KnMW8ZXHP KIr7vbr4Wy36PSQ9e75s+YTOjz67+rUSeHA00MJ1aM5H7OTpYuuVd/QINiGwrYr4P4/l AyIsDfedj9YF6bfbhf8Ez7kkINRlbHLgwkRcxikXbB3uu05W7EsArOlEcei5EILpK/Uv LkEi18m87rZpDRc7XNIosTQqiPW5aJxeG7VNvko/yii5oEdpgwxg8RY8Kp2i2+UAqPHH bUjoe9yX67GtRGb1c3EeXVNN8KwLQVwduXfqst4ZZeKisiCgW7rNHIXjE5lVxzuFJXLI htRQ== X-Gm-Message-State: AOJu0YwT+8A4XkUcOSjF6WYO6yf9lVl2Xeypp0nY3bhe8o5EBTfZ3Z5K PDZ5Iqu2Kw/vUVnV/VFWJbTLu9K3S7MBlA== X-Google-Smtp-Source: AGHT+IGKii7LmKsblZmzwOsJnNpObRIvPuu0TIvBAAZO69TXvV8LeQ16ccZjcr2tl9QOMYI5/7sc6g== X-Received: by 2002:a17:903:2281:b0:1d4:9769:b46a with SMTP id b1-20020a170903228100b001d49769b46amr611601plh.43.1703783819910; Thu, 28 Dec 2023 09:16:59 -0800 (PST) Received: from hermes.local (204-195-123-141.wavecable.com. [204.195.123.141]) by smtp.gmail.com with ESMTPSA id y9-20020a17090264c900b001d3b258e036sm14579438pli.176.2023.12.28.09.16.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Dec 2023 09:16:59 -0800 (PST) Date: Thu, 28 Dec 2023 09:16:57 -0800 From: Stephen Hemminger To: Dariusz Sosnowski Cc: Thomas Monjalon , Ferruh Yigit , Andrew Rybchenko , "Ori Kam" , Subject: Re: [RFC] ethdev: fast path async flow API Message-ID: <20231228091657.14769682@hermes.local> In-Reply-To: <20231227105709.1951231-1-dsosnowski@nvidia.com> References: <20231227105709.1951231-1-dsosnowski@nvidia.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 > However, at the moment I see one problem with this approach. > It would require DPDK to expose the rte_eth_dev struct definition, > because of implied locking implemented in the flow API. This is a blocker, showstopper for me. Have you considered having something like rte_flow_create_bulk() or better yet a Linux iouring style API? A ring style API would allow for better mixed operations across the board and get rid of the I-cache overhead which is the root cause of the needing inline.