From: Stephen Hemminger <stephen@networkplumber.org>
To: Nagma Meraj <nagma.meraj@tcs.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Jayasvi Battu <jayasvi.battu@tcs.com>,
RAJESH GUTTULA <rajesh.guttula@tcs.com>,
Nidhi Tomar <nidhi.tomar1@tcs.com>
Subject: Re: rte_timer_reset related issues in DPDK 20.05
Date: Mon, 6 Nov 2023 08:27:11 -0800 [thread overview]
Message-ID: <20231106082711.1e54c814@hermes.local> (raw)
In-Reply-To: <MAXPR01MB306932393131045F7725A219EAAAA@MAXPR01MB3069.INDPRD01.PROD.OUTLOOK.COM>
On Mon, 6 Nov 2023 10:31:20 +0000
Nagma Meraj <nagma.meraj@tcs.com> wrote:
> TCS Confidential
>
> Hi,
>
> We are working on Front Haul Library which is using DPDK internally for data accleration.
> In that we are facing the following issues:
> 1.In Front Haul Library, one of the threads xran_timing_source_thread() is using DPDK rte_timer_reset() where in the timer_add() it is printing negative values in the timer_get_prev_enteries().
Do you have threads fighting over timer?
What context is rte_timer_reset() being called in?
> 2. That is,in prev[lvl]->sl_next[lvl] = -459511634 is taking negative value in a while loop as in the below code snippet and is going in an infinite loop because of which the above thread is getting stuck here and it is failing. Can we get possible scenarios when this type of errors generally occurs?
>
> [cid:2e8dda97-6a2a-474d-ba0a-98e7789a4014]
>
>
> Thanks & Regards,
> Nagma Meraj
>
>
> TCS Confidential
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
Please don't put this on mailing list mail.
If lawyers are watching, in theory we should ignore your mail.
next prev parent reply other threads:[~2023-11-06 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 10:31 Nagma Meraj
2023-11-06 16:27 ` Stephen Hemminger [this message]
2023-11-07 12:21 ` Jayasvi Battu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231106082711.1e54c814@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jayasvi.battu@tcs.com \
--cc=nagma.meraj@tcs.com \
--cc=nidhi.tomar1@tcs.com \
--cc=rajesh.guttula@tcs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).