From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3CCB342DEC; Fri, 7 Jul 2023 00:41:10 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CF717406B5; Fri, 7 Jul 2023 00:41:09 +0200 (CEST) Received: from mail-pg1-f181.google.com (mail-pg1-f181.google.com [209.85.215.181]) by mails.dpdk.org (Postfix) with ESMTP id C5C6B40685 for ; Fri, 7 Jul 2023 00:41:08 +0200 (CEST) Received: by mail-pg1-f181.google.com with SMTP id 41be03b00d2f7-55b83ae9be2so921145a12.2 for ; Thu, 06 Jul 2023 15:41:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20221208.gappssmtp.com; s=20221208; t=1688683268; x=1691275268; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=qU3xNK91rk7XfVkP+y+pgmLZadtyNqQCeOE2wTghyzw=; b=Cu6vHo87v2WoPLLI9ezIF9ckb5dm22K9zLGJDdZW9j0bMdkvhKK8Opc+8HmzaYHSBs xHaiwgYBQHwJ1qxPOcQuVljaA8R2Hsb1ns7isGv9sWdie6dHNlupLaxX60efJonZdA0o SYuHhxTjO4854X3eHxiIEkxecuKsEd965JGmZ55gBf2yAn09c+Y2XikQlKNT1dMrFAio BeTJJqLQwA/z8Mlq6yEcPxyFqvbIbwsBzlNdxGO7jRArGDUPk13msnxdkX91OUAu4zOl 9tIcwNVfxE4mh3qaJFTffpezrBUXiu3q8d0W4IGdYHm6BEPnYIVW2MeRUv6VIT0ZwWgM qldw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688683268; x=1691275268; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=qU3xNK91rk7XfVkP+y+pgmLZadtyNqQCeOE2wTghyzw=; b=Dpv6hj/wNX5DmYLFi2v+9IQWom0UcT8UKjroqqhFbo/PkefUJzGd8+NCkd55jmlSl5 NPK1FYrAbQxV+ANx74tRUbgRyhL1AhGnEG4iVYGt98pAggR6jK60sm4ew6U5pt7bhdJm tN0NaIVSoZqdlXXCqV7nXTEZVc4lhtE1/45qav7PUXL2ScRtVgy1ysf72uE3gjq6TK5Y 4RI9CldVt4LJn4qyjY607b+htL4YdOY58qMOcs9ZLbeZ8heTtt1siWK1gbL1xEqGVDaG jRdmaPSW0BbyNZdF+wiui/VWgLHNZRq3hgPMDkrqk2KaF4wNHK8pV9bLaWUcM4n9sD64 LQyg== X-Gm-Message-State: ABy/qLYrC/zKapxh96Fb0JcwSTUkvCSDJMzkpvhEc9nFCNohci+aovBW JNiBkjZhgMn3ncoefWielCj9bw== X-Google-Smtp-Source: APBJJlFHuL0V1LS1KQ0wUTDev4PHsfsmZx4dhknk+RIy7zPNG0pbqeyoTM7szlaD8aRbwBqbbxNNog== X-Received: by 2002:a05:6a20:938b:b0:12f:d350:8a05 with SMTP id x11-20020a056a20938b00b0012fd3508a05mr3316950pzh.39.1688683267710; Thu, 06 Jul 2023 15:41:07 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id x2-20020a170902ec8200b001b85a4821f8sm1856766plg.276.2023.07.06.15.41.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 06 Jul 2023 15:41:07 -0700 (PDT) Date: Thu, 6 Jul 2023 15:41:05 -0700 From: Stephen Hemminger To: Mattias =?UTF-8?B?UsO2bm5ibG9t?= Cc: , Erik Gabriel Carrillo , David Marchand , , Stefan Sundkvist , Morten =?UTF-8?B?QnI=?= =?UTF-8?B?w7hydXA=?= , Tyler Retzlaff Subject: Re: [RFC v2 2/2] eal: add high-performance timer facility Message-ID: <20230706154105.430209bf@hermes.local> In-Reply-To: <20230315170342.214127-3-mattias.ronnblom@ericsson.com> References: <20230228093916.87206-1-mattias.ronnblom@ericsson.com> <20230315170342.214127-1-mattias.ronnblom@ericsson.com> <20230315170342.214127-3-mattias.ronnblom@ericsson.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Wed, 15 Mar 2023 18:03:42 +0100 Mattias R=C3=B6nnblom wrote: > The htimer library attempts at providing a timer facility with roughly > the same functionality, but less overhead and better scalability than > DPDK timer library. I don't understand. Why not just fix and extend existing timers. Sure you will need to add some API's and maybe drop some of the existing experimental ones (ie alt_timer). Even change the ABI. It would be better to have one high performance, scaleable timer than spend the next 3 years telling users which one to use and why! So please make rte_timer work better in 23.11 release rather than reinventing a new variant.