All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Hongzhan" <hongzhan.chen@intel.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: RE: [PATCH V2 3/3] testsuite/latmus: introduce latmus benchmark
Date: Tue, 20 Apr 2021 07:30:23 +0000	[thread overview]
Message-ID: <DM5PR11MB1852A989610602EE30EA5E05F2489@DM5PR11MB1852.namprd11.prod.outlook.com> (raw)
In-Reply-To: <da74b515-3982-1827-8b77-2ec3977aecea@siemens.com>



>-----Original Message-----
>From: Jan Kiszka <jan.kiszka@siemens.com> 
>Sent: Tuesday, April 20, 2021 2:48 PM
>To: Chen, Hongzhan <hongzhan.chen@intel.com>; xenomai@xenomai.org
>Subject: Re: [PATCH V2 3/3] testsuite/latmus: introduce latmus benchmark
>
>On 20.04.21 03:02, Chen, Hongzhan wrote:
>> 
>> 
>>> -----Original Message-----
>>> From: Jan Kiszka <jan.kiszka@siemens.com> 
>>> Sent: Friday, April 16, 2021 8:05 PM
>>> To: Chen, Hongzhan <hongzhan.chen@intel.com>; xenomai@xenomai.org
>>> Subject: Re: [PATCH V2 3/3] testsuite/latmus: introduce latmus benchmark
>>>
>>> On 16.04.21 07:31, hongzha1 via Xenomai wrote:
>>>> Measure response time to GPIO events sent by a remote Zephyr-based
>>>> latency monitor (latmon). This monitor collects then sends the latency
>>>> data over a network connection to the latmus front-end which displays
>>>> the results received:
>>>>
>>>> [Linux device under test running latmus]  <--+
>>>>                                              |
>>>>         ^                 | (GPIO ack)       |
>>>>         |                 |                  |  TCP/IP network connection
>>>>         |                 |                  |  (control & data samples)
>>>>         | (GPIO pulse)    v                  |
>>>>                                              |
>>>> [Zephyr-based device running latmon]      <--+
>>>>
>>>> The generic latency monitor code running the measurement loop is
>>>> available from the zephyr/ directory. This support comes with a Zephyr
>>>> device tree patch for enabling this monitor on NXP's FRDM-K64F
>>>> development board.
>>>
>>> Where is all this?
>> 
>> Actually , this zephyr directory is located in libevl project  at https://git.evlproject.org/libevl.git/tree/benchmarks/zephyr.  
>> at this time. Do you think it is suitable to make a copy for this folder in xenomai code base? Or I just described in comments
>> that it is from https://git.evlproject.org/libevl.git/tree/benchmarks/zephyr .
>> 
>
>It's fine to link that. But, again, this needs to go into proper in-tree
>documentation.

Could you be more specific about documentation that I need to do? Currently
I need to add ./doc/asciidoc/man1/latmus.adoc as you mentioned to tell how to 
use latmus app on Xenomai side. But actually it is more complicated than just
using latmus on xenomai side as described in  [1]
to get latmus gpio latency. Do I need to cover all [1]'s contents in
./doc/asciidoc/man1/latmus.adoc?

[1]: https://evlproject.org/core/benchmarks/

Regards

Hongzhan Chen
>
>Jan
>
>-- 
>Siemens AG, T RDA IOT
>Corporate Competence Center Embedded Linux

  reply	other threads:[~2021-04-20  7:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  5:31 [PATCH V2 0/3] introduce latmus hongzha1
2021-04-16  5:31 ` [PATCH V2 1/3] rtdm/testing: latmus: introduce latmus driver hongzha1
2021-04-16  5:31 ` [PATCH V2 2/3] drivers/gpio: core: introduce helper to find gpiochip hongzha1
2021-04-16  5:31 ` [PATCH V2 3/3] testsuite/latmus: introduce latmus benchmark hongzha1
2021-04-16 12:05   ` Jan Kiszka
2021-04-20  1:02     ` Chen, Hongzhan
2021-04-20  6:47       ` Jan Kiszka
2021-04-20  7:30         ` Chen, Hongzhan [this message]
2021-04-20  8:27           ` Philippe Gerum
2021-04-16 12:03 ` [PATCH V2 0/3] introduce latmus Jan Kiszka
2021-04-20  1:10   ` Chen, Hongzhan

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=DM5PR11MB1852A989610602EE30EA5E05F2489@DM5PR11MB1852.namprd11.prod.outlook.com \
    --to=hongzhan.chen@intel.com \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.