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 5A6C7A00C2
	for <public@inbox.dpdk.org>; Wed, 26 Jan 2022 03:00:43 +0100 (CET)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 26DEA41161;
	Wed, 26 Jan 2022 03:00:43 +0100 (CET)
Received: from mail-wm1-f50.google.com (mail-wm1-f50.google.com
 [209.85.128.50]) by mails.dpdk.org (Postfix) with ESMTP id B4E744069D
 for <users@dpdk.org>; Wed, 26 Jan 2022 03:00:41 +0100 (CET)
Received: by mail-wm1-f50.google.com with SMTP id
 q9-20020a7bce89000000b00349e697f2fbso2848550wmj.0
 for <users@dpdk.org>; Tue, 25 Jan 2022 18:00:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=mime-version:from:date:message-id:subject:to;
 bh=HGhzdFsnJ4WyTsTqcgCmIlvb7JblnZxLsd/JaDeYXfU=;
 b=PK7JhCHm6aTKWWcxHBD143m8nSSGmoUMVs3SPN8xq3x974z3oKIfwy1qKS1bCE4HWq
 HHpl3TWgvU437iK5YNONGsevczSQKhQeURpbgD8XvQJvxS7tTFMgXgm6IRiO1d50kG8f
 FT8Q6Ef4kiXO7g0d5RMSd6wDkY71sQqlwRAmcK1GWyHRpuVrTaol4/Nzm7y/KLoJNFK3
 MvoEFvWt0oGdsjTOXMQ1Hhk7RzLjO5EPOL4KnFOmfSiZRBmos3HMTKcJeHtdVp4QQcCB
 HZxAUdTFpP3AmUKZ4N044GbntqwRWBbJ9Q6iQc1hhWZUX6FQKKc9N36LSMbp22nR1mEc
 kZ2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=HGhzdFsnJ4WyTsTqcgCmIlvb7JblnZxLsd/JaDeYXfU=;
 b=QW04WWyBKCt0DPdpRX1zaVts7r8Q4E7pT0LNu1smvl3Ho6/YKtfiqxk5+mq1lcCLPH
 20K0/MHOh5/8/xWkoRg4Pb1N7MTZHjdkzdU0uA93Oa+AkpP4kbeTyUCCQC3h0f1EOwuo
 q2Vir7YZ1Q+03lbxxjnojFe2wbRYuUent9lsg9/zn9U/WClQU8ZcvUGGQU35JUeja1bU
 sIkQ/2EkxV8QJzjF7F6BPj93XeKKpN2DKqpub53iDdWTlG5FNeb82Xe2Ll54VAHNb5oa
 3yZipNlW8p8sJuBRvx7fvzoHVUAMSm9MoPca9JO/O8dXRBnbTaumerNiigyoO1zjDHi/
 9rOA==
X-Gm-Message-State: AOAM531SNtL1yMpUgQamkwMiScyxj03QBKI6X5QXZBvNBUNAzpYzNSI0
 xySZLPTk0JXIjAQhnhyaAx5eue3fy7B5A9PQYQllB0bKj4U=
X-Google-Smtp-Source: ABdhPJzkfqKV+vB9SK5jrDHRzOPTMKl7rksk9zk+8T0K5PV4jxZWOBbJoA1938XWT9oLChPsfGUnjOfOsTKgeQ/C/M8=
X-Received: by 2002:a05:600c:4e4f:: with SMTP id
 e15mr5341591wmq.53.1643162441205; 
 Tue, 25 Jan 2022 18:00:41 -0800 (PST)
MIME-Version: 1.0
From: fwefew 4t4tg <7532yahoo@gmail.com>
Date: Tue, 25 Jan 2022 21:00:30 -0500
Message-ID: <CA+Tq66WB3_QGA3OKEPBu5MgX+5mqcT7XUp8=rym44h7b7AotJQ@mail.gmail.com>
Subject: re: ports and queues
To: users@dpdk.org
Content-Type: multipart/alternative; boundary="0000000000009dcc5c05d6729141"
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

--0000000000009dcc5c05d6729141
Content-Type: text/plain; charset="UTF-8"

Which is the preferred relationship?

* N receive queues share one (TCP/UDP) port whence all TX queues send to
this port

or

* Each transmit queue chooses a TCP/UDP port where, on the RX side, each
receive queue listens on its own port for that queue.

I'm betting it's the second case. However, what also confuses me is that
RSS sits between TX and RX and chooses which RX queue a packet gets into.
It's not deterministically set at TX time. Therefore the recommended
approach appears to actually be:

* Each transmit queue chooses a TCP/UDP port by knowing ahead of time how
RSS will hash the packet for delivery to a certain RX queue.

Thanks

--0000000000009dcc5c05d6729141
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Which is the preferred relationship?<br><br>* N receive qu=
eues share one (TCP/UDP) port whence all TX queues send to this port<br><br=
>or<br><br><div>* Each transmit queue chooses a TCP/UDP port where, on the =
RX side, each receive queue listens on its own port for that queue.<br><br>=
I&#39;m betting it&#39;s the second case. However, what also confuses me is=
 that RSS sits between TX and RX and chooses which RX queue a packet gets i=
nto. It&#39;s not deterministically set at TX time. Therefore the recommend=
ed approach appears to actually be:<br><br>* Each transmit queue chooses a =
TCP/UDP port by knowing ahead of time how RSS will hash the packet for deli=
very to a certain=C2=A0RX queue.=C2=A0<br></div><div><br></div><div>Thanks<=
/div></div>

--0000000000009dcc5c05d6729141--