From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 63B23A034C; Mon, 12 Dec 2022 11:45:19 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0CFA24021D; Mon, 12 Dec 2022 11:45:19 +0100 (CET) Received: from mail-ej1-f54.google.com (mail-ej1-f54.google.com [209.85.218.54]) by mails.dpdk.org (Postfix) with ESMTP id D2A4140151 for <dev@dpdk.org>; Mon, 12 Dec 2022 11:45:16 +0100 (CET) Received: by mail-ej1-f54.google.com with SMTP id kw15so26824563ejc.10 for <dev@dpdk.org>; Mon, 12 Dec 2022 02:45:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iPqoP85qnVAly65n7nfMlZ/BuLHzbKq5y90EVQDc+BI=; b=bNbi1ljXlDVJF1UljOPgHOTYuM4PuHc7Tzv4ysomdu69mNGS/YiyBGJ5fT3+sscFtQ Hwt6QY9fFAZ0wY4PSrz49X5UQngjYi/aKhGGi5zoFsaP5618Dh2bLanhhzVI83AIKH31 BJ/RWeO/ZcCW4qzkSkFeohAkBXdtDo1DAcM2fx6yLhbMIdc/uRl5kCKVzHXB0CkiYWuE JmV2MEXtkFYi6CAENbg+BkezrUqlZbNpz8+9U1IeShfYVJ1TWXPJ60BL9hwlprcU55cZ 5ddJwM8CocVHkVWQdD4IWnRiyf1t2mTSEWinDaynCQjAraoFLNBu2wGuK5dKJlSZ83uP 463Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=iPqoP85qnVAly65n7nfMlZ/BuLHzbKq5y90EVQDc+BI=; b=1HmiLdMC403jEMJZemb0shN3aDWb+4wEEWgSZCGk1c3egKrp6dr5Ht5nYlf9T1WV/o /ez+AKVhGDEoZv4RzWkdatpEo0LISipBnrnuf90ai5UqqCsBxliwWU8bAZvq8OE76R2w nmovXVL200AuqO7tm9X9s0gvPJKyGUnAuR20GhkP/KjAQ49Wz0z8WXnT1CBSSqraoPzg TGpFChCteVCmEm0BrnVXLGC3fXseHIoJDXHquPH3u0v+60rzqCdTiatPL3m1HIzoOVdO s7TIoH6CQh63qp0KwyIQ/x+M/kl5BTCgmyAJtA00XdrXu2EGmit5jw7jcOxIJEi+/kWD 5E/g== X-Gm-Message-State: ANoB5pluvjmpARsFM+n5YWr7+HcpR8MIUwNPZrapJCk6QNJz1diwt2kl 9mXxYWQbzD3TDIL6UL65TTZ64rJ+KwjcDf2qzRdDaJHQ X-Google-Smtp-Source: AA0mqf4pD8EHPpnTCTDdt/7DKsU3tMFyKqiSQLxB43iAqSMTnwAnoeC9yDUiQOrDdeFzgjHKHArLy5TpsGsseaq6eYg= X-Received: by 2002:a17:907:3c23:b0:7c0:c0c9:d7c7 with SMTP id gh35-20020a1709073c2300b007c0c0c9d7c7mr24515815ejc.382.1670841916325; Mon, 12 Dec 2022 02:45:16 -0800 (PST) MIME-Version: 1.0 References: <CAG8PAapUJGta-RE+_xqEGUBco=cAEzsv+Yb5rUhqkT7Qc__DTg@mail.gmail.com> <Y5cESLO7xZi+d4Ii@bricha3-MOBL.ger.corp.intel.com> In-Reply-To: <Y5cESLO7xZi+d4Ii@bricha3-MOBL.ger.corp.intel.com> From: Kamaraj P <pkamaraj@gmail.com> Date: Mon, 12 Dec 2022 16:15:04 +0530 Message-ID: <CAG8PAaqG7gixBcUfb3tWFtJug2wdLoKYS-dt1EzvbyirkpRd7w@mail.gmail.com> Subject: Re: DPDK RX Ring number dump To: Bruce Richardson <bruce.richardson@intel.com> Cc: dev <dev@dpdk.org>, Stephen Hemminger <stephen@networkplumber.org>, "Burakov, Anatoly" <anatoly.burakov@intel.com> Content-Type: multipart/alternative; boundary="000000000000e605cd05ef9f3274" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org --000000000000e605cd05ef9f3274 Content-Type: text/plain; charset="UTF-8" Thanks. Is there any teatpmd application has this logic to dump these info whenever we received the packet. Thanks, Kamaraj On Mon, 12 Dec 2022, 4:07 pm Bruce Richardson, <bruce.richardson@intel.com> wrote: > On Mon, Dec 12, 2022 at 10:29:58AM +0530, Kamaraj P wrote: > > Hello All, > > We have an application where we need to dump the received packet rx > > ring number from the queue. > > Can anyone share the DPDK api to dump the rx ringnumber for the packet > > which we received (debug and troubleshoot)? > > Thanks, > > Kamaraj > > Hi, > > this information is not preserved in the DPDK mbuf structure, so is lost > after the call to rx-burst. The DPDK port field stores the port number on > return from rx_burst, but your app could look to reuse this field to store > the queue number also. For example, if you have only a few input ports, you > could encode the port number in the high bits of the "port" field, and > store the rx queue in the lower bits. This could be done as an rx-callback > if you want to avoid adjusting your app following each and every rx-burst > call. > > /Bruce > --000000000000e605cd05ef9f3274 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Thanks. Is there any teatpmd application has this logic t= o dump these info whenever we received the packet.<div dir=3D"auto"><br></d= iv><div dir=3D"auto">Thanks,</div><div dir=3D"auto">Kamaraj=C2=A0</div></di= v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On M= on, 12 Dec 2022, 4:07 pm Bruce Richardson, <<a href=3D"mailto:bruce.rich= ardson@intel.com">bruce.richardson@intel.com</a>> wrote:<br></div><block= quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc= solid;padding-left:1ex">On Mon, Dec 12, 2022 at 10:29:58AM +0530, Kamaraj = P wrote:<br> >=C2=A0 =C2=A0 Hello All,<br> >=C2=A0 =C2=A0 We have an application where we need to dump the received= packet rx<br> >=C2=A0 =C2=A0 ring number from the queue.<br> >=C2=A0 =C2=A0 Can anyone share the DPDK api to dump the rx ringnumber f= or the packet<br> >=C2=A0 =C2=A0 which we received (debug and troubleshoot)?<br> >=C2=A0 =C2=A0 Thanks,<br> >=C2=A0 =C2=A0 Kamaraj<br> <br> Hi,<br> <br> this information is not preserved in the DPDK mbuf structure, so is lost<br= > after the call to rx-burst. The DPDK port field stores the port number on<b= r> return from rx_burst, but your app could look to reuse this field to store<= br> the queue number also. For example, if you have only a few input ports, you= <br> could encode the port number in the high bits of the "port" field= , and<br> store the rx queue in the lower bits. This could be done as an rx-callback<= br> if you want to avoid adjusting your app following each and every rx-burst<b= r> call.<br> <br> /Bruce<br> </blockquote></div> --000000000000e605cd05ef9f3274--