From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v3 04/20] kernel-shark: Introduce Data streams
Date: Fri, 13 Nov 2020 17:08:01 +0200 [thread overview]
Message-ID: <1c364a42-aef8-eec7-55b6-b80447d4c608@gmail.com> (raw)
In-Reply-To: <20201113094900.594bb761@gandalf.local.home>
On 13.11.20 г. 16:49 ч., Steven Rostedt wrote:
> On Fri, 13 Nov 2020 15:47:04 +0200
> "Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:
>
>>> I wonder if this should be a string value that gets registered? Otherwise
>>> we will have to be the registry of every new stream format added.
>>>
>>> This is the approach that Tzvetomir took for protocol ids, because that way
>>> we don't need to keep track of them:
>>>
>>> https://lore.kernel.org/r/20201029111816.247241-2-tz.stoyanov@gmail.com
>>>
>>
>> I wonder how we can avoid name collisions, especially in the case when
>> some of the data readout plugins will be proprietary.
>> Also I don't think we can expect more than a dozen of distinct data
>> formats to be supported.
>
> A plugin would need to register a name on load. If two plugins were to
> collide, the register would fail letting the plugin know why. Then the
> plugin could retry with a different name "SCHED_TRACE2". Kind of like when
> you try to add a user name in a website, and that name already exists.
> Perhaps we shouldn't even bother with a hard coded name or ID. Perhaps
> simply ask for an id, and save it into some global variable for that code,
> and have all the checks test to make sure it matches the id that it
> received.
>
> In any case, seeing the VMware SchedTrace there makes that stick out as a
> big RED flag to me. I don't see why kernelshark needs to have anywhere in
> its code IDs for proprietary systems. That would be NAK'd in any other open
> source project.
>
OK, this make sense. Checking the data type will become slower, so I
just have to be very careful and remove the type checks that are not
absolutely necessary (mostly in patch 8/20).
Thanks a lot!
Y.
> -- Steve
>
next prev parent reply other threads:[~2020-11-13 15:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 14:23 [PATCH v3 00/20] Start KernelShark v2 transformation Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 01/20] kernel-shark: Use only signed types in kshark_entry Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 02/20] kernel-shark: Add stream_id to kshark_entry Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 03/20] kernel-shark: Introduce libkshark-hash Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 04/20] kernel-shark: Introduce Data streams Yordan Karadzhov (VMware)
2020-11-12 20:50 ` Steven Rostedt
2020-11-13 13:47 ` Yordan Karadzhov (VMware)
2020-11-13 14:42 ` Steven Rostedt
2020-11-13 14:49 ` Steven Rostedt
2020-11-13 15:08 ` Yordan Karadzhov (VMware) [this message]
2020-11-12 14:23 ` [PATCH v3 05/20] kernel-shark: Rename static methods in libkshark Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 06/20] kernel-shark: Add basic methods for Data streams Yordan Karadzhov (VMware)
2020-11-12 21:17 ` Steven Rostedt
2020-11-13 13:55 ` Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 07/20] kernel-shark: Housekeeping before implementing stream interface Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 08/20] kernel-shark: Add stream interface for trace-cmd data Yordan Karadzhov (VMware)
2020-11-12 22:10 ` Steven Rostedt
2020-11-13 13:58 ` Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 09/20] kernel-shark: Start introducing KernelShark 2.0 Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 10/20] kernel-shark: Start using data streams Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 11/20] kernel-shark: Remove dead code Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 12/20] kernel-shark: Redesign the plugin interface Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 13/20] kernel-shark: Complete the stream integration Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 14/20] kernel-shark: Provide merging of multiple data streams Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 15/20] kernel-shark: Integrate the stream definitions with data model Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 16/20] kernel-shark: Use only signed types for model defs Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 17/20] kernel-shark: Add ksmodel_get_bin() Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 18/20] kernel-shark: Protect ksmodel_set_in_range_bining() Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 19/20] kernel-shark: Add methods for time calibration Yordan Karadzhov (VMware)
2020-11-12 14:23 ` [PATCH v3 20/20] kernel-shark: Integrate streams with libkshark-configio Yordan Karadzhov (VMware)
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=1c364a42-aef8-eec7-55b6-b80447d4c608@gmail.com \
--to=y.karadz@gmail.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).