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 4DA3541DEB; Sun, 5 Mar 2023 18:25:13 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DAD5A40EF0; Sun, 5 Mar 2023 18:25:12 +0100 (CET) Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com [209.85.214.178]) by mails.dpdk.org (Postfix) with ESMTP id AC3F740EE5 for ; Sun, 5 Mar 2023 18:25:11 +0100 (CET) Received: by mail-pl1-f178.google.com with SMTP id y11so7801379plg.1 for ; Sun, 05 Mar 2023 09:25:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; t=1678037111; 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=5ktlwZfDhdW/cUcFd4Vtk7/07CTPAlazEaz8RXKLBno=; b=IZm+g9KxncEPDXvTS4hSFnj2LmrDqv3GPl1eVEhAgBgLUqSEx7+2yK0iQAkgjr3zxL 0lnA1sQW0sS8JXrLZVsJA0szT2C4fYRB0G8N5Z7TmC1+G7lhyyq5xFYobFshBQot6jRS 9togD9UBCHZdCmWcUE37rYS36pVB2B3a1L0OD5kUCxpQameCXynqmBIejX9vEt3hP4Rt BwUs9jnP7HabTDeAXDsc/n/9y5dD5Kfdb2VRHBM458bOELfY0MtyXY6Jwxk4499MHbcq K6vbFXaa0ERyxSOOE+GR3ESivuIgBw+jdGdgTWs/ICPYIQH2SE7aKgcGlWYaj5EZNXvm nicQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678037111; 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=5ktlwZfDhdW/cUcFd4Vtk7/07CTPAlazEaz8RXKLBno=; b=BesIwle6SXR2vub4hPs3eDvkS6LrryqgKus0KDYFZGMzGQSmj0lhh9z0qKQJlWcHE1 tN0ngLb4lLtwSJwmGGnafHQdr1k79k9yRPSFzOsuYntBQAbuYX7KDW1pq9IAnvlkMW9l yj3O+8D5QsLXN6ZRFg2JgQbgn52N5liLXtdH4N6cQc7uDl+yycl1JGN7TH+uHVUeq7PX Lvy00haphWjUgqN7nvHl3BLJBqA1AajfH+3+hoQAcXs8gIAYib+l3RdvuM2HjhE4XbnM kP3MVI2q85pcbHoibMYw7Sgx6uBuRtzs9jil/JQs5Ash+Xmfy5AIFAvAY7NgFE31tm38 jetg== X-Gm-Message-State: AO0yUKXhGQLmvBDKMir3HM5uHMpMjOVLpFu8ijORm/0JLhFa+YfRdLzX nPQR7AeZRNStcSR680xfgaTcNQ== X-Google-Smtp-Source: AK7set9V3NmVdY3UrYJlS9ETefmFrodih8jBjqNLDIWWW8i1pJDrddWS+1fIKVCFJbeKjXN+dMt3Gg== X-Received: by 2002:a17:903:2310:b0:19a:9833:704 with SMTP id d16-20020a170903231000b0019a98330704mr10890496plh.61.1678037110767; Sun, 05 Mar 2023 09:25:10 -0800 (PST) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id ko7-20020a17090307c700b0019a6cce2060sm3023030plb.57.2023.03.05.09.25.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 05 Mar 2023 09:25:10 -0800 (PST) Date: Sun, 5 Mar 2023 09:25:08 -0800 From: Stephen Hemminger To: Mattias =?UTF-8?B?UsO2bm5ibG9t?= Cc: , Erik Gabriel Carrillo , David Marchand , , Stefan Sundkvist Subject: Re: [RFC 2/2] eal: add high-performance timer facility Message-ID: <20230305092508.6922b4b4@hermes.local> In-Reply-To: <20230228093916.87206-3-mattias.ronnblom@ericsson.com> References: <20230228093916.87206-1-mattias.ronnblom@ericsson.com> <20230228093916.87206-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 Tue, 28 Feb 2023 10:39:16 +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. >=20 > The htimer library employs per-lcore hierachical timer wheels and a > message-based synchronization/MT-safety scheme. >=20 > Signed-off-by: Mattias R=C3=B6nnblom I like this but: - need to have one timer infrastructure, having multiple will lead to con= fusion and overlap in user applications. I.e can they be mixed, what happens i= f X and Y... - best to keep original API available. - ok to drop the rte_alt_timer since it was always experimental. - would be good to have API using consistent known time (nanoseconds?) ra= ther than TSC cycles. - there could be use cases for REALTIME as well as MONOTONIC types.