From: Philippe Gerum <rpm@xenomai.org>
To: Hannes Diethelm <hannes.diethelm@gmail.com>
Cc: xenomai@lists.linux.dev
Subject: Re: EVL: Kernel WARNING
Date: Mon, 06 Jul 2026 07:56:06 +0200 [thread overview]
Message-ID: <87jyr8r79l.fsf@xenomai.org> (raw)
In-Reply-To: <871pdhs7tf.fsf@xenomai.org> (Philippe Gerum's message of "Sun, 05 Jul 2026 18:46:36 +0200")
Philippe Gerum <rpm@xenomai.org> writes:
> Hannes Diethelm <hannes.diethelm@gmail.com> writes:
>
>> Am 05.07.26 um 17:06 schrieb Philippe Gerum:
>>> Hannes Diethelm <hannes.diethelm@gmail.com> writes:
>>>
>>>> - With the good version, I tested ~1M packages, all fine, max 60 us
>>>> response time on the real PC
>>> You mean 60us for the overall round-trip time between two
>>> evl-enabled
>>> targets in full/end-to-end oob mode?
>>>
>>
>> That's between an evl-enabled host and an FPGA board as a target[1]
>> directly connected with 100M Ethernet and an Intel I350 after some
>> heavy tuning. Most tuning was done for PREEMT_RT. I have to test what
>> is really needed for Xenomai4 and what can be dropped.
>>
>> I don't have two PC's to test (yet).
>>
>> https://store.mesanet.com/index.php?route=product/product&product_id=374
>
> Ok, thanks for the information. Meanwhile, I found the culprit. Now I
> have to figure out why I did that. Oh, well..
>
> commit a793acf3cab9a608d70a39d740f04c6a6a1ec77c
> Author: Philippe Gerum <rpm@xenomai.org>
> Date: Tue May 26 10:16:44 2026 +0200
>
> evl/net: packet: forward status of ETH_P_ALL delivery
Fixed by #bb06b3a8f100.
--
Philippe.
next prev parent reply other threads:[~2026-07-06 5:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 18:05 EVL: Kernel WARNING Hannes Diethelm
2026-07-05 12:00 ` Hannes Diethelm
2026-07-05 15:04 ` Philippe Gerum
2026-07-05 15:10 ` Philippe Gerum
2026-07-05 15:06 ` Philippe Gerum
2026-07-05 15:17 ` Hannes Diethelm
2026-07-05 16:46 ` Philippe Gerum
2026-07-06 5:56 ` Philippe Gerum [this message]
2026-07-06 21:21 ` Hannes Diethelm
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=87jyr8r79l.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=hannes.diethelm@gmail.com \
--cc=xenomai@lists.linux.dev \
/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.