DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC PATCH 0/1] Add l2reflect measurement application
Date: Fri, 3 Jul 2020 16:07:56 +0000	[thread overview]
Message-ID: <AM0PR10MB1939107765E2168D3B2A2DBF896A0@AM0PR10MB1939.EURPRD10.PROD.OUTLOOK.COM> (raw)

> 03/07/2020 17:18, Felix Moessbauer:
> > Dear Maintainers,
> >
> > this patch adds a measurement application to benchmark the latency of
> > transmitting l2 packets via DPDK.
> Are you using a real time system to reduce latency?

Yes, we use a Debian buster with preempt-rt patched kernel.
Additionally, we use isolcpus for the RT relevant threads.
Apart from achieving low latency, we use this tool to measure the maximum latency over a long period of time.
This gives a good estimate that the system behaves deterministically, even under high load.
The tool also has a built-in mechanism to set trace points when a threshold is hit, to later inspect the kernel logs.

> > We add this application to the examples folder, as similar tools were
> > placed there as well.
> No, the examples are not supposed to be tools.
> They demonstrate some APIs.
> If it is a tool to measure performance, and can be used in a CI, I think it is better
> hosted in the directory apps/.
Ok, got it. There were some issues reported by checkpatch. I'll fix them and move to apps.
Thanks for the hint!

             reply	other threads:[~2020-07-03 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03 16:07 Moessbauer, Felix [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-03 15:18 Felix Moessbauer
2020-07-03 15:51 ` Thomas Monjalon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM0PR10MB1939107765E2168D3B2A2DBF896A0@AM0PR10MB1939.EURPRD10.PROD.OUTLOOK.COM \
    --to=felix.moessbauer@siemens.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \


* 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).