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 A32D04325F for ; Wed, 1 Nov 2023 11:16:10 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1E144402D5; Wed, 1 Nov 2023 11:16:10 +0100 (CET) Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) by mails.dpdk.org (Postfix) with ESMTP id A10E2400EF for ; Wed, 1 Nov 2023 11:16:08 +0100 (CET) Received: by mail-wr1-f51.google.com with SMTP id ffacd0b85a97d-32ddfb38c02so4674970f8f.3 for ; Wed, 01 Nov 2023 03:16:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698833768; x=1699438568; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ai2j2ur/rxwREzZBsq2GlQGdyy1RYbK7y67YzoT0Ju0=; b=RplZsqyw/kDQ+ssdbEU3x2UWjigwGCKnfCc49HXt2mmofPo4cxByfYe/bP9ZrH0QP0 FfGDSy41A9REij51jU8KAgyijRV/+gRpADDjXs4mUjJNvbSZvMkNSqPNE8TuEvHlfbjM RxN+tpAYgxw8TtBl7lpXWqitEtWoZNQYLnQbfblFd2wSEx6Qg2LyxWwnzq9KfCE9837j PF0tCFHSrkAJGLSAVJdmDKvQyBh0vOxDxT3npMInmFlss+9YIyrg7H2OjAcEeR1cuMGQ 1O/RCn0dHDFOIM9mlKz1wns2zhrphvi9ib5JNimZTlCHv1gUMtjEfoH+q+PLHDQH0H1W RG8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698833768; x=1699438568; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ai2j2ur/rxwREzZBsq2GlQGdyy1RYbK7y67YzoT0Ju0=; b=oGdIFfe7u1FZkOZMWwCSwdWqvlqbl/KdPWC1q0wUCyn6bLjfCrjz6UJelMEpt/8Xm8 W2Xrxhf4jSsmPOE62x1vG/yCZr2rJclHgbqB4ayHXRzntoB+gODqHAb8/x+hDe8zr4xH dCuMEScS0jBxFWlehw3CaKKW7XpTDWbU7NKm7ZtD+8QPgpvw2Wj9fAl+riorfQXYQdT7 JeQM8DD8q7Yd39tX1zdTClOTWA2B5FeyKXEPgJ+Q2Ab346ALMLIrBTcHdsa7nS3iP/xl 85wJCIThzt89yyKcsI0OH3rqMIG7SiSqxUEb7uT6i2B1urwG8ZSrc1lyoshyGPwbHRuv LYzw== X-Gm-Message-State: AOJu0YwmFQq+2vJirZ0jcUFoD8g7RKhsxtuB+34G2pUiezFHBX1m7Ukl KvjxEYrwMv3VyoRKKzQlwG73HCp2uja6yDpQvBBBNttv1q6Pqg== X-Google-Smtp-Source: AGHT+IHWAApQnfzhanArfBoEb43HgHPPIo2cp8FNTdjH1gXO+UxO6Dai3ZzOt38baBb77MEgEOsm6XHzkrwSLgSKyxQ= X-Received: by 2002:adf:e48e:0:b0:32d:8f0a:d2e7 with SMTP id i14-20020adfe48e000000b0032d8f0ad2e7mr11483735wrm.42.1698833767910; Wed, 01 Nov 2023 03:16:07 -0700 (PDT) MIME-Version: 1.0 References: <4608f13e503247448ae58959fe2df35f@huawei.com> In-Reply-To: <4608f13e503247448ae58959fe2df35f@huawei.com> From: Alireza Sanaee Date: Wed, 1 Nov 2023 10:15:55 +0000 Message-ID: Subject: Re: Primary and secondary processes polling on two queues To: "jiangheng (G)" Cc: "users@dpdk.org" Content-Type: multipart/alternative; boundary="00000000000044d2b90609148f6b" 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 --00000000000044d2b90609148f6b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Thanks for the message. Currently, I have a sender and client, and actually, there is no packet loss as my server application with primary and secondary processes is responding to packets back to the client side, and the client is receiving 100% of packets. I am sending UDP packets. However, the problem right now is that when I check with DPDK rte_eth_stat_gets(), then the API reports packet loss on DPDK queues while we know that there is no packet loss. Thanks, Alireza On Wed, Nov 1, 2023 at 1:31=E2=80=AFAM jiangheng (G) wrote: > Hi, > > 1) Yes > > 2) What type of packets are you receiving, Tcp or UDP? You need > correctly configure NIC RSS or flow rule. Otherwise, packets may be > received only in queue 0. > > > > > > *=E5=8F=91=E4=BB=B6=E4=BA=BA:* Alireza Sanaee > *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:* 2023=E5=B9=B411=E6=9C=881=E6=97= =A5 3:58 > *=E6=94=B6=E4=BB=B6=E4=BA=BA:* users@dpdk.org > *=E4=B8=BB=E9=A2=98:* Primary and secondary processes polling on two queu= es > > > > Hi everyone, > > > > I have a NIC and I would like to receive packets on my primary process an= d > secondary process. I wonder if I can have primary process poll on queue = =3D 0 > and secondary one poll on queue =3D 1. > > > > I tried to do this and observed packet loss. That made me wonder if I am > configuring something wrong. > > > > Two questions: > > > > 1) Is this possible from practicality perspective? > > 2) If yes, what can potentially go wrong in this scenario. > > > > > > Thanks, > > Alireza > --00000000000044d2b90609148f6b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

Thanks for the message.
<= br>
Currently, I have a sender and client, and actually, there is= no packet loss as my server application with primary and secondary process= es is responding to packets back to the client side, and the client is rece= iving 100% of packets. I=C2=A0am sending UDP packets.

<= div>However, the problem right now is that when I check with DPDK rte_eth_s= tat_gets(), then the API reports packet loss on DPDK queues while we know t= hat there is no packet loss.

Thanks,
Ali= reza

On Wed, Nov 1, 2023 at 1:31=E2=80=AFAM jiangheng (G) <jiangheng14@huawei.com> wrote:

Hi,

1)=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Yes

2)=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 What type of packets are you receiving, Tcp= or UDP? You need correctly configure NIC RSS or flow rule. Otherwise, pack= ets may be received only in queue 0.

=C2=A0

=C2=A0

=E5=8F=91=E4=BB=B6=E4=BA=BA: Alireza Sanaee <sarsanaee@gmail.com>
=E5= =8F=91=E9=80=81=E6=97=B6=E9=97=B4:= 2023= =E5=B9=B411=E6=9C=881=E6=97=A5 3:58
=E6=94=B6=E4=BB=B6=E4=BA=BA: users@= dpdk.org
=E4=B8=BB=E9=A2=98: Primary and secondary processes polling on two queues=

=C2=A0

Hi everyone,

=C2=A0

I have a NIC and I would like t= o receive packets on my primary process and secondary process. I wonder if = I can have primary process poll on queue =3D 0 and secondary one poll on qu= eue =3D 1.

=C2=A0

I tried to do this and observed= packet loss. That made me wonder if I am configuring something wrong.

=C2=A0

Two questions:

=C2=A0

1) Is this possible from practi= cality perspective?

2) If yes, what can potentially= go wrong in this scenario.

=C2=A0

=C2=A0

Thanks,

Alireza

--00000000000044d2b90609148f6b--