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 25CB9A0540; Tue, 13 Dec 2022 08:31:58 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 18D2A4021D; Tue, 13 Dec 2022 08:31:58 +0100 (CET) Received: from mail-ed1-f50.google.com (mail-ed1-f50.google.com [209.85.208.50]) by mails.dpdk.org (Postfix) with ESMTP id 0B0F140146 for <dev@dpdk.org>; Tue, 13 Dec 2022 08:31:57 +0100 (CET) Received: by mail-ed1-f50.google.com with SMTP id c66so16475542edf.5 for <dev@dpdk.org>; Mon, 12 Dec 2022 23:31:57 -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=euGjLtcjYZ+cFoS3sdB0Im8NoNvKp4ikoL62PeVoDt8=; b=DhoYVEaB/r4irMf3wnAiHXTIiUWWd8DP8gJqGRnOcns8AWz1egNP5+cbmTiwRyowEZ wOz59yhU62wM000oLjyVc47Uu2nrMNRFMtDs4JVKqtBDJJVE+MHlHSCSAOvxGjruENwh vFLfn/zbedBsEZHkqAZSQKCLcHVfSPmEa8cxEZQMadJd5W5zmNPmNL3xmiebNJbI69cc 1tTnwVJfGGAwaf06W0R4J6PagwhDjEQpvPuXUnNsCNiNqU5eAOIPUqBkMoE/8aQj/84x kZ+NNv992qay9hNsfBsfrOUBH+ydNfVPGWroR0Cah2HiWjfETh+QkCTU77RJMX2/arUA B5QQ== 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=euGjLtcjYZ+cFoS3sdB0Im8NoNvKp4ikoL62PeVoDt8=; b=ZNLf6/Uq6KyaxYwNMUvmukHqfMKDQnF88f8spKsUsIMmVw81w1ludWYxWyG3k3gN06 0iRUGi++QHe6J+aq9oYFsfbm0IP0n9Qe1uPrw8nj9F0wp9+kwz3EjoHTeMDHR/Bi5zIt yJdQWv8NfiZzYaWYp+6LjMpLgNYu+mJfApXybVCQcj7jAl4qdtzZJbEnXnokuODWTrC6 Xccv3bQFjHuas+tpjZP4/xGYbqAcV8c0kPgO3lHrKgwMxsQOgQfVIxXiIru5H1AN6Je9 +N2JO634c0YL5LjKOADySUMi6yRriMRwn5y0IeAerZitF+zSbAhtyZGYCly3sQRFrj4N Ah+A== X-Gm-Message-State: ANoB5pnjxjKvUeJOAjhIEZYa3Od14LqO5oBlq+0mQmmZbxCCc5J8wQAZ a2gO+0PYP+0EJL2HkCowGW6sZeudTi+9hT04IPUcF9e0 X-Google-Smtp-Source: AA0mqf6mf4a7RNCmMujfhoj4+zVVjFDidWR9KuUVs62hAUJGu58A1IqK8nieGVK45qlKEKDYP1O9RhBX3SCamDuPKIg= X-Received: by 2002:a05:6402:2a09:b0:461:30d8:6742 with SMTP id ey9-20020a0564022a0900b0046130d86742mr5274999edb.172.1670916716597; Mon, 12 Dec 2022 23:31:56 -0800 (PST) MIME-Version: 1.0 References: <CAG8PAapUJGta-RE+_xqEGUBco=cAEzsv+Yb5rUhqkT7Qc__DTg@mail.gmail.com> <Y5cESLO7xZi+d4Ii@bricha3-MOBL.ger.corp.intel.com> <CAG8PAaqG7gixBcUfb3tWFtJug2wdLoKYS-dt1EzvbyirkpRd7w@mail.gmail.com> <Y5cKZ3NeEZPqbohz@bricha3-MOBL.ger.corp.intel.com> <20221212083125.490ef9d2@hermes.local> In-Reply-To: <20221212083125.490ef9d2@hermes.local> From: Kamaraj P <pkamaraj@gmail.com> Date: Tue, 13 Dec 2022 13:01:44 +0530 Message-ID: <CAG8PAaomwE4gP+PcOhbRqYMrQfFfGngOBYaD+scyhjK8AENHUA@mail.gmail.com> Subject: Re: DPDK RX Ring number dump To: Stephen Hemminger <stephen@networkplumber.org> Cc: Bruce Richardson <bruce.richardson@intel.com>, dev <dev@dpdk.org>, "Burakov, Anatoly" <anatoly.burakov@intel.com> Content-Type: multipart/alternative; boundary="0000000000005796f105efb09d86" 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 --0000000000005796f105efb09d86 Content-Type: text/plain; charset="UTF-8" Thanks Stephen,. As Bruce suggested earlier we cannot get ringnumber from the queue(attached to the port) after rx_burst call. Thanks, Kamaraj On Mon, 12 Dec 2022, 10:01 pm Stephen Hemminger, <stephen@networkplumber.org> wrote: > On Mon, 12 Dec 2022 11:03:03 +0000 > Bruce Richardson <bruce.richardson@intel.com> wrote: > > > On Mon, Dec 12, 2022 at 04:15:04PM +0530, Kamaraj P wrote: > > > Thanks. Is there any teatpmd application has this logic to dump > these > > > info whenever we received the packet. > > > Thanks, > > > Kamaraj > > > > > Sorry, no. No example application has the logic to do this. > > Since the DPDK uses a pull model, the receive queue is known > when calling rx_burst(). > --0000000000005796f105efb09d86 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Thanks Stephen,.<div dir=3D"auto">As Bruce suggested earl= ier we cannot get ringnumber from the queue(attached to the port) after rx_= burst call.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks,</div= ><div dir=3D"auto">Kamaraj</div><div dir=3D"auto"><br></div></div><br><div = class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, 12 Dec = 2022, 10:01 pm Stephen Hemminger, <<a href=3D"mailto:stephen@networkplum= ber.org">stephen@networkplumber.org</a>> wrote:<br></div><blockquote cla= ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa= dding-left:1ex">On Mon, 12 Dec 2022 11:03:03 +0000<br> Bruce Richardson <<a href=3D"mailto:bruce.richardson@intel.com" target= =3D"_blank" rel=3D"noreferrer">bruce.richardson@intel.com</a>> wrote:<br= > <br> > On Mon, Dec 12, 2022 at 04:15:04PM +0530, Kamaraj P wrote:<br> > >=C2=A0 =C2=A0 Thanks. Is there any teatpmd application has this lo= gic to dump these<br> > >=C2=A0 =C2=A0 info whenever we received the packet.<br> > >=C2=A0 =C2=A0 Thanks,<br> > >=C2=A0 =C2=A0 Kamaraj<br> > >=C2=A0 =C2=A0<br> > Sorry, no. No example application has the logic to do this.<br> <br> Since the DPDK uses a pull model, the receive queue is known<br> when calling rx_burst().<br> </blockquote></div> --0000000000005796f105efb09d86--