DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jayasvi Battu <jayasvi.battu@tcs.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	Nagma Meraj <nagma.meraj@tcs.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	RAJESH GUTTULA <rajesh.guttula@tcs.com>,
	Nidhi Tomar <nidhi.tomar1@tcs.com>
Subject: RE: rte_timer_reset related issues in DPDK 20.05
Date: Tue, 7 Nov 2023 12:21:11 +0000	[thread overview]
Message-ID: <BM1PR01MB2228AD0382DF5F14C495B2FCF6A9A@BM1PR01MB2228.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20231106082711.1e54c814@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 3105 bytes --]

TCS Confidential


Hi Stephen,

Thank you for your reply.

Please find my answers inline.

1.Do you have threads fighting over timer?

No , we are running the thread on only one core so there is no deadlock here. But as discussed earlier the thread is getting stuck in an infinite while loop with prev[lvl]->sl_next[lvl]  = -459511634 in timer_get_prev_enteries().





2.What context is rte_timer_reset() being called in?



During Uplink and Downlink data transfer, we are using the thread of fronthaul library, where it executes callbacks for every 1 ms, and for every call back we are trying to reset the timer.





3.The commit id"[cid:2e8dda97-6a2a-474d-ba0a-98e7789a4014]" which you have shared, we are unable to find it in the git. If possible, can you please share the link of the same?



--

Thanks and Regards

Jayasvi Battu / Nagma




TCS Confidential

-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org>
Sent: Monday, November 6, 2023 9:57 PM
To: Nagma Meraj <nagma.meraj@tcs.com>
Cc: 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



External Email : Be cautious while opening any links or attachments.



On Mon, 6 Nov 2023 10:31:20 +0000

Nagma Meraj <nagma.meraj@tcs.com<mailto: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.



[-- Attachment #2: Type: text/html, Size: 7650 bytes --]

      reply	other threads:[~2023-11-07 13:05 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
2023-11-07 12:21   ` Jayasvi Battu [this message]

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=BM1PR01MB2228AD0382DF5F14C495B2FCF6A9A@BM1PR01MB2228.INDPRD01.PROD.OUTLOOK.COM \
    --to=jayasvi.battu@tcs.com \
    --cc=dev@dpdk.org \
    --cc=nagma.meraj@tcs.com \
    --cc=nidhi.tomar1@tcs.com \
    --cc=rajesh.guttula@tcs.com \
    --cc=stephen@networkplumber.org \
    /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).