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 46A6942AD6 for ; Thu, 11 May 2023 17:35:17 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0BD2742DAE; Thu, 11 May 2023 17:35:17 +0200 (CEST) Received: from mail-pl1-f171.google.com (mail-pl1-f171.google.com [209.85.214.171]) by mails.dpdk.org (Postfix) with ESMTP id 0472340DF6 for ; Thu, 11 May 2023 17:35:15 +0200 (CEST) Received: by mail-pl1-f171.google.com with SMTP id d9443c01a7336-1aad55244b7so67454175ad.2 for ; Thu, 11 May 2023 08:35:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20221208.gappssmtp.com; s=20221208; t=1683819315; x=1686411315; 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=EijGLzLrPCwMknORb8qD9zyZaDlp8cTSV96uyyv6sgM=; b=YF6fbCFlX+rq5OpgxU8MFX9zu31OM7pgTudc7BT59xNUa6PPRXTU8uaosLCWhEhF9d bU0WPwy17v9u8qWh20snWb+noH0+z+MciPfjeHZarklYegKUR60CE8Z/EP0qs0X6xcm8 uzd/JFudmJ+ERt50STqXBwMqg7vl4aMR/wGl3vq9wUzk9A7XDUv21eg4/nzfeUL200UX ChC1MgoS5tJuGUuEEpWZ0I0mSiyfWeaNU8munpSpCvjavUvP7FuJ2r55dR3i6kmlrZ1C aM9pBJOFhp0pcnuMKcbpKFVEzn0T4nR9X3+h+2kjewf9DaVZuQm3f81fiaTbZlqXptEA 93JQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683819315; x=1686411315; 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=EijGLzLrPCwMknORb8qD9zyZaDlp8cTSV96uyyv6sgM=; b=SVLgGxcv/YRmhMhYzcNCQ+ctWtW+i8yQEkEZQlwlMJKAEbvXu7K2mji2IAD1xPv5rQ Oeqwe74bal63KEdXZK+aNO2zl8CdHUuSRG4T9hco7Th0rBpwx7LAR1tQDaPDVBqqMRF1 x3HaU6iNR9qRYo64rh+g1Lvsto5vGWoDaSMnBv9r3KPksoURqxfdjW8wrH4Y+ymRSlnQ WwNfSbLJhCABgCeezGHiQyy3+MXMrYoiW/e3W5JUzYQbQB/pctlQl7YX75csah5rtTvv kuKZtgdCIrNAp0YN8sXupwO+1MtsDr5po2qpmm09rbSdzRNtNsTUFJMYHdWQukDBqBuu XbhQ== X-Gm-Message-State: AC+VfDyx6WJcBNFMabwmwuDJB+zJ8C2dbEYnbqeLxbGyAIHfC1OxPde9 LrAyPbek2rPAk5Bc1SwMjKjzLjzIBe3BxI2ooTCibg== X-Google-Smtp-Source: ACHHUZ4eit/qq4kVRl7ND+gCvda7asx/FRXJ++6YpZGtwqW5TnjZNTgm0zKR6c9NTV8KjkWzW4Ny/A== X-Received: by 2002:a17:902:d4d0:b0:1ab:c4e:de87 with SMTP id o16-20020a170902d4d000b001ab0c4ede87mr25755872plg.10.1683819315131; Thu, 11 May 2023 08:35:15 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id r11-20020a1709028bcb00b001a064282b11sm6085771plo.151.2023.05.11.08.35.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 11 May 2023 08:35:14 -0700 (PDT) Date: Thu, 11 May 2023 08:35:13 -0700 From: Stephen Hemminger To: =?UTF-8?B?7J207J6s7ZmN?= Cc: users@dpdk.org Subject: Re: Is it right way to test between two modes? Message-ID: <20230511083513.741e6c9f@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Thu, 11 May 2023 13:47:23 +0900 =EC=9D=B4=EC=9E=AC=ED=99=8D wrote: > Hello, > I'm really sorry to ask a lot... but I want to make sure that what I did = is > right or not >=20 > I compared two modes > 1. default poll mode > 2. interrupt mode (In my understand.. it is kind of an event driven mode = in > dpdk) >=20 > [Test 1] - poll mode > $ sudo ./examples/dpdk-l3fwd -l 1-3 -n 4 -- -p 0x3 --config=3D"(0,0,1)" > * power: about 36W* >=20 > [Test 2] - event driven mode > $ sudo ./examples/dpdk-l3fwd-power -l 1-3 -n 4 -- -p 0x03 > --config=3D"(0,0,1)" --interrupt-only > * power: about 12W* >=20 >=20 > When Idle situation, Test1 uses a core 100% and Test2 doesn't use a core a > lot (almost 0%), so I think I can say "In idle mode, Test2 Mode(event > driven) reduces power by 1/3 compared to poll mode." Is it correct?? >=20 > BR, > Jaehong Lee A couple of other notes. 1. Generating real world traffic pattern is important. Testing with somethi= ng like a full line rate test of UDP is not real life. Ideally a pattern of mu= ltiple real machines to see the self-correlated TCP bursts, etc. 2. Measuring actual power would require something attached to the power sup= ply. The CPU load is not that great a final measure. One option would be to use something like powertop which can look at some of the kernel internals.