DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: "Carrillo, Erik G" <erik.g.carrillo@intel.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] test/event: fix timeout accuracy
Date: Tue, 16 Mar 2021 11:46:07 +0000	[thread overview]
Message-ID: <PH0PR18MB40860FCF3C5ADAF277F6CABFDE6B9@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SA2PR11MB51967B15F1574FAEB08405FCB9939@SA2PR11MB5196.namprd11.prod.outlook.com>

>> -----Original Message-----
>> From: pbhagavatula@marvell.com <pbhagavatula@marvell.com>
>> Sent: Saturday, March 6, 2021 2:27 PM
>> To: jerinj@marvell.com; Carrillo, Erik G <erik.g.carrillo@intel.com>
>> Cc: dev@dpdk.org; Pavan Nikhilesh <pbhagavatula@marvell.com>;
>> stable@dpdk.org
>> Subject: [dpdk-dev] [PATCH] test/event: fix timeout accuracy
>>
>> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>>
>> Round timeout ticks when converting from nanoseconds, this
>prevents loss
>> of accuracy and deviation from requested timeout value.
>>
>> Fixes: d1f3385d0076 ("test: add event timer adapter auto-test")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
>Thanks, Pavan:
>
>Acked-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>

Thanks, Gabriel,

Could you take a look at [1] too? It fixes a similar problem

[1]http://patches.dpdk.org/project/dpdk/patch/20210225120144.2591-1-pbhagavatula@marvell.com/


      parent reply	other threads:[~2021-03-16 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06 20:26 pbhagavatula
2021-03-08 17:20 ` Carrillo, Erik G
2021-03-08 18:09   ` Jerin Jacob
2021-03-16 11:46   ` Pavan Nikhilesh Bhagavatula [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=PH0PR18MB40860FCF3C5ADAF277F6CABFDE6B9@PH0PR18MB4086.namprd18.prod.outlook.com \
    --to=pbhagavatula@marvell.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=jerinj@marvell.com \
    --cc=stable@dpdk.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).