From: Daniel.Thibault@drdc-rddc.gc.ca (Thibault, Daniel)
Subject: [lttng-dev] Interplay of enable-channel options
Date: Fri, 31 May 2013 19:48:15 +0000 [thread overview]
Message-ID: <48CF5AC71E61DB46B70D0F388054EFFD12D2256E@VAL-E-02.valcartier.drdc-rddc.gc.ca> (raw)
Harking back to Mathieu's post of 3 May 2013 10:42:22, I'd like to see if I understand the options correctly. I'm pretty sure I don't.
When a channel has been set to use per-UID buffering, if an event-producing user-space process dies suddenly it may create a "hole" in one of the channel's sub-buffers, temporarily preventing the consumer from getting access to the sub-buffer. Once the other event producers have filled the remaining sub-buffers, the session daemon will try to re-use the "hung" sub-buffer, at which point it will be discarded. Unrelated events in the sub-buffer will be lost.
If the channel is also set to --discard, does this mean the session daemon will not flush the hung sub-buffer? This would mean the consumer daemon waits at the holed sub-buffer and never gets past it.
What if --read-timer has been set to a non-zero value? Will the holed sub-buffer be flushed at that point in time? In this case the producers may not even have time to fill the remaining sub-buffers.
How can the session daemon create a hole in a sub-buffer, anyway? Doesn't it get all of the event's description and payload in its own working memory before starting to write it out to the sub-buffer?
Daniel U. Thibault
Protection des syst?mes et contremesures (PSC) | Systems Protection & Countermeasures (SPC)
Cyber s?curit? pour les missions essentielles (CME) | Mission Critical Cyber Security (MCCS)
R & D pour la d?fense Canada - Valcartier (RDDC Valcartier) | Defence R&D Canada - Valcartier (DRDC Valcartier)
2459 route de la Bravoure
Qu?bec QC? G3J 1X5
CANADA
Vox?: (418) 844-4000 x4245
Fax?: (418) 844-4538
NAC?: 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
Gouvernement du Canada?| Government of Canada
<http://www.valcartier.drdc-rddc.gc.ca/>
reply other threads:[~2013-05-31 19:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48CF5AC71E61DB46B70D0F388054EFFD12D2256E@VAL-E-02.valcartier.drdc-rddc.gc.ca \
--to=daniel.thibault@drdc-rddc.gc.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox