From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it1-f173.google.com (mail-it1-f173.google.com [209.85.166.173]) by dpdk.org (Postfix) with ESMTP id F366856A3 for ; Sat, 3 Nov 2018 05:28:11 +0100 (CET) Received: by mail-it1-f173.google.com with SMTP id w7-v6so5873456itd.1 for ; Fri, 02 Nov 2018 21:28:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=X8pMMsHxAHwU0I2TQOA2D1C5gJm2+34HvbXbp9a6lAQ=; b=ZCJe1QCr8ok7HIsjuvft3phFYCiOa5EbgdLSSEZNarjVRxacHYGBMaer9KGCTUsjms rYZ0+ykqreeMSL0LkQIO9QM4bjYybMhxeYbStGxiEwAjdKZ4mocy6FVHU2Xw0HZyyESZ 7/U2cJ6cVpx4pVusz+qZUlvfRTIAzLYMdrNe4= 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=X8pMMsHxAHwU0I2TQOA2D1C5gJm2+34HvbXbp9a6lAQ=; b=MO47EIJH+omxSaWbyQ3fbYwQcxGg7BmaGIFZqO/LVlxS326ZUaghs56YhgmoBB737E 11JKq5ap+KAfxWLbR+uOwZMjmZkSGRaZq85rBCZz6kSpQ7YlG86hsDcs/O2y938yFy/6 Xj+T79NJOKvcLhcjdXkXtCygdMTzyx8fcO4XwSglN/LftO4FVPiTsO1tkuIaDFVx5cxU pT0zR7e5ZNbZjSaYCa4UNz5RIXEiRPx4qyP1ag69FZD5UvNtQcO9VcB5uUxquanKH64A +c6ZD6D2bIKr26HhOCEOuThUxjf+fVOGYPTH/FuvxQSdRUtJPn9ldgSZLd8uTjpj+HKe TXzg== X-Gm-Message-State: AGRZ1gKm8TUUJRaD+NVp6XId4oAdBKTL8Q3mj/r+sg/dMReffPL+Hw5e rt27LMeJMCr99VtfqVhA8v6bKeR7tBsNmEJWO/CTxg== X-Google-Smtp-Source: AJdET5fj9iYc8P+nZmuyCbfleM9+Yj5cdHfO+5OJhB/9dzvR8U3MJYChd5cOd/GPF7pUrerJYHzbq1LAosp7OLaUTBE= X-Received: by 2002:a02:495d:: with SMTP id z90-v6mr12128447jaa.89.1541219291205; Fri, 02 Nov 2018 21:28:11 -0700 (PDT) MIME-Version: 1.0 References: <051139db-381e-5f2f-32dc-1b91e8e45fee@intel.com> <3B45A79A-D782-4274-984C-DB1CD49B7252@intel.com> <5891119E-2F06-4467-A737-55FF37668D37@intel.com> In-Reply-To: From: Somnath Kotur Date: Sat, 3 Nov 2018 09:58:02 +0530 Message-ID: To: keith.wiles@intel.com Cc: anatoly.burakov@intel.com, dev Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] Question about rte_manage_timer() and eal_intr_handle_interrupts X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 04:28:12 -0000 Hi Anatoly/keith, I just tried using rte_eal_alarm_set() in the driver like so: rte_eal_alarm_set(US_PER_S * 2, timer0_cb, (void *)data); The moment i start this off, i stop getting async events/interrupt notifications in my driver ...I'm hitting the same problem as it was before with rte_timer_manage() as well. What is going wrong here ? Something we are missing ? Thanks Som On Sat, Nov 3, 2018 at 8:06 AM Somnath Kotur wrote: > Thank you Anatoly and keith for your replies. What i still don't get is > why the two cannot seem to co-exist? > That is , whenever this while loop was running in the EAL thread that i > showed in the code, my driver would stop receiving interrupts/async events > ...Do we understand that? > But you are right Anatoly, i need something to be called in my driver at a > cadence of ~2s, I was registering timers in my driver and running > rte_timer_manage() in this seperate thread to check and ensure the > callbacks are executed on expiry. > so if you are saying, i can achieve same functionality using rte_alarm() > while i can get async events in my driver at the same time, i will explore > this option > Thanks a lot > > Som > > On Fri, Nov 2, 2018 at 8:07 PM Wiles, Keith wrote: > >> >> >> > On Nov 2, 2018, at 9:35 AM, Wiles, Keith wrote: >> > >> > >> Sorry, meant to hit cancel for my previous email, Anatoly answered it >> correctly. >> >> Regards, >> Keith >> >>