LEADER 03588oam  2200445zu 450 
001 9910130829703321
005 20241212220420.0
010   $a9780769542841
035   $a(CKB)3420000000000924
035   $a(SSID)ssj0000781138
035   $a(PQKBManifestationID)12351970
035   $a(PQKBTitleCode)TC0000781138
035   $a(PQKBWorkID)10803495
035   $a(PQKB)11428440
035   $a(NjHacI)993420000000000924
035   $a(EXLCZ)993420000000000924
100   $a20160829d2012      uy 
101 0 $aeng
135   $aur|||||||||||
181   $ctxt
182   $cc
183   $acr
200 10$a2012 IEEE 18th International Conference on Embedded and Real-Time Computing Systems and Applications
210 31$a[Place of publication not identified]$cIEEE$d2012
215   $a1 online resource $cillustrations
300   $aBibliographic Level Mode of Issuance: Monograph
311 08$a9780769548241 
311 08$a0769548245 
311 08$a9781467330176 
311 08$a1467330175 
330   $aThis paper describes a low-overhead and prolonged Linux process logging mechanism that is separated into networks for embedded systems with small memory. It is useful to log the behavior of Linux processes in Android in order to debug, test, and learn about the embedded systems. However, the logging system interferes with process scheduling and requires huge storage to capture the process behavior. We propose a separated Linux process logging mechanism to solve these problems. Two features are utilized to develop the mechanism.The first is an improved logging performance. When acquiring context switch log data from an operating system, some data may be lost because of limited memory. To solve this problem, we propose a low-overhead data generating, low-latency data gathering and sending mechanism. This has a lightweight binary and string data format that uses a context-dependent log compression algorithm.The second feature is the construction of a log data management system that is available over a network. The logging mechanism is separated into two parts - a Logging Environment (LE) and a Logging Monitoring Environment (LME) - to reduce the effect of the target device and increase the volume of log data stored area. The LE consists of a log generation part in the target embedded device and a log collection part on the server. The LME consists of various monitoring and debugging tools, such as a log analyzer or log visualizer. In order to utilize the tools on the LME, the generated log data is exported to the log collection server via the network by an embedded device. The collected log data can be converted to an application-friendly format, such as Common Trace Format (CTF) or JavaScript Object Notation (JSON), on the log collection server to reduce the overhead of the embedded device in the LE and be easily available to the LME tools. We utilize an HTTP-based communication protocol between the LE and LME.As a result of an evaluation, the latency of data gathering and the overhead of data generation are decreased by 50%. The scheduling interference and the volume of log data also decrease. Our method is also comfortable transferring data across the network as well as CPU loading.
606   $aReal-time control$vCongresses
615  0$aReal-time control
676   $a629.8
702   $aIEEE Staff
801  0$bPQKB
906   $aPROCEEDING
912   $a9910130829703321
996   $a2012 IEEE 18th International Conference on Embedded and Real-Time Computing Systems and Applications$92349104
997   $aUNINA