linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Slavomir Kaslev <kaslevs@vmware.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org, pauld@redhat.com,
	ykaradzhov@vmware.com, jbacik@fb.com, tstoyanov@vmware.com,
	slavomir.kaslev@gmail.com
Subject: [PATCH v4 0/2] Optimize pid filters
Date: Wed, 17 Apr 2019 16:09:57 +0300	[thread overview]
Message-ID: <20190417130959.10064-1-kaslevs@vmware.com> (raw)

This patchset optimizes how pid filters are expressed and makes it less likely
that we overflow ftrace filters' size limit of one page.

Changes since v3:
Addressed Steven's review feedback
Add section about --no-filter to `trace-cmd record`'s man page
Dropped the patch adding --no-filter since Steven has already applied it

Changes since v2:

Append exclude rules with &&

Changes since v1:

Add missing tags
Fix append_filter_pid_range() callers to pass valid range as [min,max]

Slavomir Kaslev (2):
  trace-cmd: Optimize how pid filters are expressed
  trace-cmd: Document record --no-filter option in record's man page

 Documentation/trace-cmd-record.1.txt |   4 +
 tracecmd/trace-record.c              | 117 ++++++++++++++++++---------
 2 files changed, 85 insertions(+), 36 deletions(-)

-- 
2.19.1


             reply	other threads:[~2019-04-17 13:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 13:09 Slavomir Kaslev [this message]
2019-04-17 13:09 ` [PATCH v4 1/2] trace-cmd: Optimize how pid filters are expressed Slavomir Kaslev
2019-04-17 13:58   ` Phil Auld
2019-04-17 14:18     ` John Kacur
2019-04-17 14:25       ` Phil Auld
2019-04-17 14:52         ` Steven Rostedt
2019-04-17 14:52     ` Steven Rostedt
2019-04-17 14:54     ` Steven Rostedt
2019-04-17 13:09 ` [PATCH v4 2/2] trace-cmd: Document record --no-filter option in record's man page Slavomir Kaslev
2019-04-17 14:05   ` Phil Auld
2019-04-17 16:19   ` Steven Rostedt
2019-04-17 16:24     ` Steven Rostedt

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=20190417130959.10064-1-kaslevs@vmware.com \
    --to=kaslevs@vmware.com \
    --cc=jbacik@fb.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=pauld@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=slavomir.kaslev@gmail.com \
    --cc=tstoyanov@vmware.com \
    --cc=ykaradzhov@vmware.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 NNTP newsgroup(s).