linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Saenz Julienne <nsaenzju@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] trace-cmd: Add option to poll trace buffers
Date: Thu, 10 Jun 2021 10:20:18 +0200	[thread overview]
Message-ID: <9d7604e64497510a118826fe51c8950d188f667c.camel@redhat.com> (raw)
In-Reply-To: <20210609161717.10e259b2@oasis.local.home>

On Wed, 2021-06-09 at 16:17 -0400, Steven Rostedt wrote:
> On Wed, 2 Jun 2021 10:05:42 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> > On Wed,  2 Jun 2021 11:08:03 +0200
> > Nicolas Saenz Julienne <nsaenzju@redhat.com> wrote:
> > 
> > > NOTE: I'm aware that TRACECMD_RECORD_POLL kind of clashes with
> > >       TRACECMD_RECORD_BLOCK. That's why I renamed it. There might be a
> > >       clean way to merge them into a single flag, but it's not clear to
> > >       me why was TRACECMD_RECORD_BLOCK needed in the first place (since
> > >       it only affects splicing).  
> > 
> > Yeah that was poorly named, and was added when streaming was added (not
> > recording to a file, but to simply read from splice). I don't remember
> > exactly all that happened back them, but you are correct, it can
> > probably be better organized.
> > 
> > Thanks for sending the patch, I'll have a look at it this week.
> 
> FYI, I pushed this patch up to the git repo.
> 
> Thanks,

Thanks!

-- 
Nicolás Sáenz


      reply	other threads:[~2021-06-10  8:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  9:08 [PATCH] trace-cmd: Add option to poll trace buffers Nicolas Saenz Julienne
2021-06-02 14:05 ` Steven Rostedt
2021-06-09 20:17   ` Steven Rostedt
2021-06-10  8:20     ` Nicolas Saenz Julienne [this message]

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=9d7604e64497510a118826fe51c8950d188f667c.camel@redhat.com \
    --to=nsaenzju@redhat.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --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 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 NNTP newsgroup(s).