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 D0030A00C5 for <public@inbox.dpdk.org>; Sun, 18 Dec 2022 23:14:06 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 56A5940146; Sun, 18 Dec 2022 23:14:06 +0100 (CET) Received: from mail-pj1-f48.google.com (mail-pj1-f48.google.com [209.85.216.48]) by mails.dpdk.org (Postfix) with ESMTP id CC5A1400D5 for <users@dpdk.org>; Sun, 18 Dec 2022 23:14:05 +0100 (CET) Received: by mail-pj1-f48.google.com with SMTP id 3-20020a17090a098300b00219041dcbe9so7212356pjo.3 for <users@dpdk.org>; Sun, 18 Dec 2022 14:14:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; 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=gSEjmPgsGBdxBefsILt4g/M1apU7/HbcsHH+y2YvGec=; b=sOqhUhWzT6BIOrm4Z71ZS955CqejsO7qn/lte5rBYEUKPouyMfLdg2V6K0MeeJ+L2j 2qiHvi49UmRk/j44sfmGrVECfcMtYjSK8qNZSOUWqVvZCIWjsFduPPepJD5QtSbDp1sg nPESdtto5DjS/KAXZPQl2jJ6HLUp2YJ3kSE1k/jRlrSi0tiTpIgZoDQZSKs0+DR8MEly t4mmZ4ulOwBQi1bAGCeB+o5vGq/sxyQvs673xWt7t96PEiRfWJ9zFzkGCovynN4Yr4f0 6jIyDBi81v7InQe+vNJ/ehh73lLWvdn30NSZIdr+H82m2fCNmA+QwpyPWg4mc3M0KxqY 8Mhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=gSEjmPgsGBdxBefsILt4g/M1apU7/HbcsHH+y2YvGec=; b=1o1/aNj31WnEHW16pdlDK5x29wP+vgo4/18IWHwHi0OxTas3MyydvNkHSuHwJbicNV QJl4s/Cy02I0lmRew0BFa2RsC730klyHBuB03RflDAtI0N5+KBCAIKYTle9qb+5c4LCc pFnjIs/Ksu6MsLVQ1eEYbkoukZbEb/AkxSvYxvlW0meChOM+9eEghZjMjEEkyKgwekXN /06jpK5HMkbZi9yTRqQLMJTrF/Oc/pjGZXXgLYljZLbh/MXbmg2Es0xE0jiub1pQiTjA O23bEhPUSKlfjBdQNTd8j/svwXsgUCBM7e1GzmJ9AUnifySuq0xXsJ3PQPZigRzHc7lB 1AYg== X-Gm-Message-State: ANoB5plcyZRoEWsusyLh4WBWb5A7LnNxTTVKWcCHqZsVqHMk44/S3v4O WCCE0MDfMaTN5Qs6i7wHM0rX+w== X-Google-Smtp-Source: AA0mqf7MQP2WR5IeIdNLSLWYvpDNU/TP6A6mMC3h/EacuQcWnkxMetLgfgNjkuHp9ACluMFxPWzIQg== X-Received: by 2002:a17:902:6bcc:b0:188:5256:bf60 with SMTP id m12-20020a1709026bcc00b001885256bf60mr39112815plt.25.1671401644800; Sun, 18 Dec 2022 14:14:04 -0800 (PST) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id c7-20020a170902d48700b001896522a23bsm5577813plg.39.2022.12.18.14.14.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 18 Dec 2022 14:14:04 -0800 (PST) Date: Sun, 18 Dec 2022 14:14:02 -0800 From: Stephen Hemminger <stephen@networkplumber.org> To: fwefew 4t4tg <7532yahoo@gmail.com> Cc: "users@dpdk.org" <users@dpdk.org> Subject: Re: Is there a way to instruct NIC/DPDK which RXQ to deliver a packet to not RSS? Message-ID: <20221218141402.52240242@hermes.local> In-Reply-To: <CA+Tq66X0n+EE6gzDUNcLKh=xChjPTrdwXv9kuWN8t9rN5Grkjg@mail.gmail.com> References: <CA+Tq66X0n+EE6gzDUNcLKh=xChjPTrdwXv9kuWN8t9rN5Grkjg@mail.gmail.com> 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 <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 On Sun, 18 Dec 2022 16:41:13 -0500 fwefew 4t4tg <7532yahoo@gmail.com> wrote: > I am aware of RSS; I coded it and have gotten it to work between machines. > > However, the elapsed time per packet increases from <100ns/packet RSS-OFF > to 700-800ns RSS-ON in my test setup. > > In my scenario I have hardcoded routing between TXQs on client machines and > RXQs on the server machines. Packet direction to queue in HW is done with rte_flow (if your NIC supports it) https://doc.dpdk.org/guides/prog_guide/rte_flow.html RSS should be implemented in hardware. So it shouldn't be causing added latency. What device are you using.