All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Fernandes <joel@joelfernandes.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	diamon-discuss@lists.linuxfoundation.org,
	lttng-dev <lttng-dev@lists.lttng.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [diamon-discuss] [RELEASE] LTTng-modules 2.9.11, 2.10.8, 2.11.0-rc2 (Linux kernel tracer)
Date: Fri, 22 Mar 2019 09:48:14 -0400	[thread overview]
Message-ID: <20190322134814.GB56461@google.com> (raw)
In-Reply-To: <20190321091356.38a6988d@gandalf.local.home>

On Thu, Mar 21, 2019 at 09:13:56AM -0400, Steven Rostedt wrote:
> On Thu, 21 Mar 2019 08:41:22 -0400
> Joel Fernandes <joel@joelfernandes.org> wrote:
> 
> > Also does it also make sense for lttng ring buffer to use the ftrace code for
> > ring buffer, or make the ftrace ring buffer better and have lttng use it? Or
> > is the lttng ring buffer design too radically different?
> 
> We tried in the past and never actually got something that we both
> could agree on. Now I believe the user space tools depend on the way
> each one is, so to change one will break the tools that read it.

I understand :-\

thanks,

 - Joel


WARNING: multiple messages have this Message-ID (diff)
From: Joel Fernandes <joel@joelfernandes.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: diamon-discuss@lists.linuxfoundation.org,
	lttng-dev <lttng-dev@lists.lttng.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [diamon-discuss] [RELEASE] LTTng-modules 2.9.11, 2.10.8, 2.11.0-rc2 (Linux kernel tracer)
Date: Fri, 22 Mar 2019 09:48:14 -0400	[thread overview]
Message-ID: <20190322134814.GB56461@google.com> (raw)
In-Reply-To: <20190321091356.38a6988d@gandalf.local.home>

On Thu, Mar 21, 2019 at 09:13:56AM -0400, Steven Rostedt wrote:
> On Thu, 21 Mar 2019 08:41:22 -0400
> Joel Fernandes <joel@joelfernandes.org> wrote:
> 
> > Also does it also make sense for lttng ring buffer to use the ftrace code for
> > ring buffer, or make the ftrace ring buffer better and have lttng use it? Or
> > is the lttng ring buffer design too radically different?
> 
> We tried in the past and never actually got something that we both
> could agree on. Now I believe the user space tools depend on the way
> each one is, so to change one will break the tools that read it.

I understand :-\

thanks,

 - Joel


  reply	other threads:[~2019-03-22 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 22:56 [RELEASE] LTTng-modules 2.9.11, 2.10.8, 2.11.0-rc2 (Linux kernel tracer) Mathieu Desnoyers
2018-11-01 22:56 ` [diamon-discuss] " Mathieu Desnoyers
2018-11-01 23:33 ` Joel Fernandes
2018-11-01 23:33   ` Joel Fernandes
2019-03-19 17:34   ` Mathieu Desnoyers
2019-03-21 12:41     ` Joel Fernandes
2019-03-21 13:13       ` Steven Rostedt
2019-03-21 13:13         ` Steven Rostedt
2019-03-22 13:48         ` Joel Fernandes [this message]
2019-03-22 13:48           ` Joel Fernandes

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=20190322134814.GB56461@google.com \
    --to=joel@joelfernandes.org \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lttng-dev@lists.lttng.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.org \
    /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.