From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id E2999A00E6 for ; Mon, 2 Sep 2019 13:42:49 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 236CE1C0BD; Mon, 2 Sep 2019 13:42:49 +0200 (CEST) Received: from mail-qt1-f176.google.com (mail-qt1-f176.google.com [209.85.160.176]) by dpdk.org (Postfix) with ESMTP id CF5F01C0B0 for ; Mon, 2 Sep 2019 13:42:47 +0200 (CEST) Received: by mail-qt1-f176.google.com with SMTP id b2so11804368qtq.5 for ; Mon, 02 Sep 2019 04:42:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iith.ac.in; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lio2Mt2VwuN2ITX0YCVBy2Q6DXTLLCn3cbCLe0ThL94=; b=1109k65LWKtANDvn6UuKJuCpkKViSEVHORzwqXHuJsfpcvOHu4wZBnpyYnyyGK+Wke 9uZ6DlDjEuQYdr2NBUMN5yJL+Lfv1xZ6mGasBV5tjByJpLynsvTQtrcPJ5qEH3p6AmRm FUaMtfe4rQkd6J/63C5Y/baxQQLroV9sHZqHI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lio2Mt2VwuN2ITX0YCVBy2Q6DXTLLCn3cbCLe0ThL94=; b=Xw8zumMjLb/wZV1zwyR5YFU5e6yZ+3LdRxTPG3eehz022UNBpO39nIrT523mLnYa6v glRW4JZMsSTdMeabFfBAJkDtmBYwbdwkfRtUSTNVGIHU4xrYLMF2BxPdGGal8XIZjk6N K2zmlbXMypsF7l80CL3cI4Un7celDlJ7PkrJ3olBebRXvbRk/RbMKYDCiJ4yORVxj06V gvhZoQ7Y4uv22zQq5+jnbpqeWui6t/lMNuLsWUdOAqjnzDyNVmAiyv+odHvOFrS7Tina BFrbJ2Jwng+lB7PlxVgNrXDZRl/EHW8FoIo02PBDvC57nDbbvQlUa4TGvuiCs23HHonY Cjrw== X-Gm-Message-State: APjAAAWs9hm9JZwsf7WXBTSA0CvSsbeXQETN/thpVhTuOSitwNlADpFE z9Ncf65E1TH3qn2sKe3TLkLGL2XZJaVcqkiR4X0r3w== X-Google-Smtp-Source: APXvYqyIrpQXMp9l6yABl0IoXXMgyk543xar49mCnbgBVg00BoAI2Q2QsQTTc1mHUD5liWpBv8sXsIrPsxF956htDj0= X-Received: by 2002:a05:6214:144f:: with SMTP id b15mr9783227qvy.171.1567424567061; Mon, 02 Sep 2019 04:42:47 -0700 (PDT) MIME-Version: 1.0 References: <20190902112214.GA631@bricha3-MOBL.ger.corp.intel.com> In-Reply-To: <20190902112214.GA631@bricha3-MOBL.ger.corp.intel.com> From: Suraj R Gupta Date: Mon, 2 Sep 2019 17:12:36 +0530 Message-ID: To: Bruce Richardson Cc: users@dpdk.org, dev@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] [dpdk-dev] Stopping DPDK Timer [RTE-Timers] X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi, If I am right, rte_timer_stop() stops the timer after the call back execution. It is said that if rte_timer_stop() is called during timer running, function will fail. I want to know if timer can be stopped in middle abruptly? i.e If I have timer started for 500 ms and i want to stop it in 100ms Thanks On Mon, Sep 2, 2019 at 4:52 PM Bruce Richardson wrote: > On Mon, Sep 02, 2019 at 11:02:16AM +0530, Suraj R Gupta wrote: > > Hi all, > > I am working with DPDK timers. > > In the documentation of timers, it has been said that dpdk based > rte-timers > > cannot stopped while running. I would like to know if there is any way to > > stop it in middle or any workaround is possible. > > > > For e.g.: If I have timer started for 500 ms and i want to stop it in > 100 > > ms due to an event/interrupt. > > > > Note:I am not talking of stopping timer after callback execution, before > > timer expiry in middle > > Thanks in advance. > > > I think rte_timer_stop() is what you are looking for. > > /Bruce > -- Thanks and Regards Suraj R Gupta