From: Stephen Hemminger <stephen@networkplumber.org>
To: 이재홍 <ljh890322@gmail.com>
Cc: users@dpdk.org
Subject: Re: Is it right way to test between two modes?
Date: Thu, 11 May 2023 08:35:13 -0700 [thread overview]
Message-ID: <20230511083513.741e6c9f@hermes.local> (raw)
In-Reply-To: <CA+WmBsSOaZCmPNbESoPq8nUut8BuMWpk1RnUQ0UBF5B-H+WMrQ@mail.gmail.com>
On Thu, 11 May 2023 13:47:23 +0900
이재홍 <ljh890322@gmail.com> wrote:
> Hello,
> I'm really sorry to ask a lot... but I want to make sure that what I did is
> right or not
>
> I compared two modes
> 1. default poll mode
> 2. interrupt mode (In my understand.. it is kind of an event driven mode in
> dpdk)
>
> [Test 1] - poll mode
> $ sudo ./examples/dpdk-l3fwd -l 1-3 -n 4 -- -p 0x3 --config="(0,0,1)"
> * power: about 36W*
>
> [Test 2] - event driven mode
> $ sudo ./examples/dpdk-l3fwd-power -l 1-3 -n 4 -- -p 0x03
> --config="(0,0,1)" --interrupt-only
> * power: about 12W*
>
>
> 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??
>
> BR,
> Jaehong Lee
A couple of other notes.
1. Generating real world traffic pattern is important. Testing with something
like a full line rate test of UDP is not real life. Ideally a pattern of multiple
real machines to see the self-correlated TCP bursts, etc.
2. Measuring actual power would require something attached to the power supply.
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.
prev parent reply other threads:[~2023-05-11 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 4:47 이재홍
2023-05-11 15:35 ` Stephen Hemminger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230511083513.741e6c9f@hermes.local \
--to=stephen@networkplumber.org \
--cc=ljh890322@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).