linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH v1] trace-cmd: introduce --initital-delay for record command
Date: Mon, 18 Dec 2017 23:45:39 +0100	[thread overview]
Message-ID: <9d275f1a-346a-7ca8-c6c8-d32758770fd7@redhat.com> (raw)
In-Reply-To: <20171218164308.658924b8@gandalf.local.home>

On 18.12.2017 22:43, Steven Rostedt wrote:
> On Mon, 18 Dec 2017 21:56:33 +0100
> David Hildenbrand <david@redhat.com> wrote:
>  
>> I'll have a try tomorrow if I I''lose events with 20MB buffers per CPU
>> when recording more than 60 seconds (on a very active system with
>> mentioned scheduler rtaces being turned on).
>>
> 
> Another option is to add a '-w' option to record that causes the
> recorders (what reads the data) to "wait" or force it to sleep even if
> it did read something. I'm fine with that.

Also thought about that. Might make sense (and makes -s actually do what
it advertises even when there are a lot of events coming in).

Thanks Steve

> 
> -- Steve
> 


-- 

Thanks,

David / dhildenb

      reply	other threads:[~2017-12-18 22:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171218112412.11898-1-david@redhat.com>
2017-12-18 15:41 ` [PATCH v1] trace-cmd: introduce --initital-delay for record command Steven Rostedt
2017-12-18 16:23   ` David Hildenbrand
2017-12-18 17:52     ` Steven Rostedt
2017-12-18 20:56       ` David Hildenbrand
2017-12-18 21:43         ` Steven Rostedt
2017-12-18 22:45           ` David Hildenbrand [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=9d275f1a-346a-7ca8-c6c8-d32758770fd7@redhat.com \
    --to=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).