lttng-dev Archive mirror
 help / color / mirror / Atom feed
From: "Lemay, Paul via lttng-dev" <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] Shared memory circular buffer and K8s pods
Date: Tue, 18 Oct 2022 13:00:47 +0000	[thread overview]
Message-ID: <DS7PR19MB637575A3329444AD675C12379F289@DS7PR19MB6375.namprd19.prod.outlook.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 622 bytes --]

Hello There,

We are looking at LTTng for a development here at Dell. As I understand the LTTng, there are shared memories of circular buffer traces created between  an application and the consumer daemon. After looking at some presentation that you did, I see that you have started working on containerization and pods.

So our applications run in pods, and am not sure how to organize the pods knowing about those shared memories? Can you help us better understand how our code should be organized in the context of Kubernetes? Any documentation that we can access?

Best Regards


Internal Use - Confidential

[-- Attachment #1.2: Type: text/html, Size: 2590 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2022-10-18 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 13:00 Lemay, Paul via lttng-dev [this message]
2022-10-18 18:34 ` [lttng-dev] Shared memory circular buffer and K8s pods Jérémie Galarneau via lttng-dev
2022-10-18 18:40   ` Lemay, Paul via lttng-dev

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=DS7PR19MB637575A3329444AD675C12379F289@DS7PR19MB6375.namprd19.prod.outlook.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=P.Lemay@Dell.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).