From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: sebastian@breakpoint.cc, linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/5] trace-cmd: Improvements in compression logic
Date: Wed, 2 Mar 2022 06:51:26 +0200 [thread overview]
Message-ID: <20220302045131.387658-1-tz.stoyanov@gmail.com> (raw)
Improvements in internal comperssion APIs, suggested by
Sebastian Andrzej Siewior.
Tzvetomir Stoyanov (VMware) (5):
trace-cmd: Use a structure to describe a compression protocol
trace-cmd: Make internal compression hooks more generic
trace-cmd: Use errno from zlib, if available
trace-cmd: Add context to compression hooks
trace-cmd: Use context hooks in zstd
.../include/private/trace-cmd-private.h | 20 ++--
lib/trace-cmd/trace-compress-zlib.c | 41 ++++---
lib/trace-cmd/trace-compress-zstd.c | 100 ++++++++++++------
lib/trace-cmd/trace-compress.c | 80 +++++++-------
4 files changed, 144 insertions(+), 97 deletions(-)
--
2.34.1
next reply other threads:[~2022-03-02 4:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 4:51 Tzvetomir Stoyanov (VMware) [this message]
2022-03-02 4:51 ` [PATCH 1/5] trace-cmd: Use a structure to describe a compression protocol Tzvetomir Stoyanov (VMware)
2022-03-02 7:03 ` Sebastian Andrzej Siewior
2022-03-02 4:51 ` [PATCH 2/5] trace-cmd: Make internal compression hooks more generic Tzvetomir Stoyanov (VMware)
2022-03-02 7:08 ` Sebastian Andrzej Siewior
2022-03-02 4:51 ` [PATCH 3/5] trace-cmd: Use errno from zlib, if available Tzvetomir Stoyanov (VMware)
2022-03-02 7:15 ` Sebastian Andrzej Siewior
2022-03-02 15:52 ` Steven Rostedt
2022-03-03 7:09 ` Sebastian Andrzej Siewior
2022-03-02 4:51 ` [PATCH 4/5] trace-cmd: Add context to compression hooks Tzvetomir Stoyanov (VMware)
2022-03-02 7:13 ` Sebastian Andrzej Siewior
2022-03-03 1:10 ` Steven Rostedt
2022-03-03 16:33 ` Tzvetomir Stoyanov
2022-03-02 4:51 ` [PATCH 5/5] trace-cmd: Use context hooks in zstd Tzvetomir Stoyanov (VMware)
2022-03-02 7:13 ` Sebastian Andrzej Siewior
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=20220302045131.387658-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sebastian@breakpoint.cc \
/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).