[genivi-dlt] [PATCH] Some patches for DLT Daemon / 2.16 Release request

Lipka, Christoph (ADITJ/SWG) clipka at jp.adit-jv.com
Tue Jan 24 19:44:33 EST 2017

Hi Lutz,

You are right. In general, the documentation is a bit outdated and it is not so convenient to read txt files that may have to be compiled to html or something beforehand. Might be better to add such information directly on the Github page as many projects do or add documentation to DLT Viewer that can be read from inside the application.

Regarding the Ringbuffer size: it might be sometimes necessary to increase or decrease the buffer - but in general it should be untouched. It depends on the system.

We also have from time to time the problem of high logging load, but we haven’t any numbers or scenarios to get an understanding when messages get lost. I guess there is no general valid number...
We mostly overcome the problem by asking if really *all* applications/contexts need to log in - worst case - verbose mode to understand a certain problem. I guess in all cases this is not the case, so shut off all logs not needed often helps here. There need to be an understanding at the testers side that more log messages come with the drawback of increased system load ...
Or do you talking about one application generates so much logs that DLT is not able to forward them all to a client? Where are the messages lost? In the library, because of full buffer?

Best regards

Christoph Lipka
Software Group (ADITJ/SWG)

Tel. +81-(0)566 61-5124

-----Original Message-----
From: genivi-diagnostic-log-and-trace [mailto:genivi-diagnostic-log-and-trace-bounces at mailman1.genivi.org] On Behalf Of Helwing, Lutz
Sent: Tuesday, January 24, 2017 6:25 PM
To: genivi-diagnostic-log-and-trace at mailman1.genivi.org
Subject: Re: [genivi-dlt] [PATCH] Some patches for DLT Daemon / 2.16 Release request

Hi Christoph,

i'm sorry for the late reply to your patch. What i am missing is a documentation of the "Environment variables for library ringbuffer" feature.

I'm afraid that most users are not searching the commit logs or the source code when looking for a feature.

A general question: do you consider it good practice to play around with the ringbuffer size? Couldn't the need for a larger buffer be a hint at some problem elsewhere? Currently i'm struggling in a customer project with lost messages. The only thing i recognise is that they are generating an immense load of trace output.

Does anyone here have experience how much load DLT can take before loosing messages?

Kind regards


On 18.10.2016 03:11, Lipka, Christoph (ADITJ/SWG) wrote:
Hi all,

We like to propose some patches for DLT Daemon.
The attached patches can be applied on current master (<https://github.com/GENIVI/dlt-daemon/commit/e1d7cba3c9a1bc764313e6eb0ae42a5af0881ac2>https://github.com/GENIVI/dlt-daemon/commit/e1d7cba3c9a1bc764313e6eb0ae42a5af0881ac2).
The patches contain mainly unit tests, smoketests, bug and compiler warning fixes.

Furthermore, I like to release 2.16 DLT Daemon during next week, if nobody has any concerns. 2.16 Release should be used as base for discussing FIFO -> UNIX socket and MessageFilter feature requests.

If you have any questions, please let me know.

Best regards

Christoph Lipka
Advanced Driver Information Technology
Software Group (ADITJ/SWG)
1-1 Showa-cho, Kariya-shi
Aichi-ken 448-8661, Japan
Tel. +81-(0)566 61-5124
Fax +81-(0)566 25-4774
clipka at jp.adit-jv.com<mailto:clipka at jp.adit-jv.com>

ADIT is joint venture company of DENSO Corporation and Bosch GmbH

genivi-diagnostic-log-and-trace mailing list genivi-diagnostic-log-and-trace at mailman1.genivi.org<mailto:genivi-diagnostic-log-and-trace at mailman1.genivi.org>

genivi-diagnostic-log-and-trace mailing list genivi-diagnostic-log-and-trace at mailman1.genivi.org

More information about the genivi-diagnostic-log-and-trace mailing list