From: Ross Zwisler <zwisler@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org,
Stevie Alvarez <stevie.6strings@gmail.com>
Subject: Re: [PATCH v2 11/17] libtraceeval histogram: Add iterator APIs
Date: Wed, 16 Aug 2023 15:34:49 -0600 [thread overview]
Message-ID: <20230816213449.GA3686281@google.com> (raw)
In-Reply-To: <20230811053940.1408424-12-rostedt@goodmis.org>
On Fri, Aug 11, 2023 at 01:39:34AM -0400, Steven Rostedt wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
>
> Provide an interface for the application to iterate over all the entries
> in the traceeval histogram.
>
> traceeval_iterator_get() - acquire an iterator for the given traceeval
> traceveal_iterator_put() - release the iterator
> traceeval_iterator_sort() - sort the iterator for a given key/value
> traceeval_iterator_next() - return the keys of the next entry in the
> traceeval
>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
> include/traceeval-hist.h | 7 ++
> src/eval-local.h | 11 ++
> src/hash.c | 4 +
> src/histograms.c | 255 ++++++++++++++++++++++++++++++++++++++-
> 4 files changed, 276 insertions(+), 1 deletion(-)
>
<>
> diff --git a/src/histograms.c b/src/histograms.c
> index 9a8ec4d85301..2b823ad5c26d 100644
> --- a/src/histograms.c
> +++ b/src/histograms.c
> @@ -37,7 +37,7 @@ static void print_err(const char *fmt, ...)
> * -1 for the other way around, and -2 on error.
> */
> static int compare_traceeval_data(struct traceeval *teval,
> - union traceeval_data *orig,
> + const union traceeval_data *orig,
> const union traceeval_data *copy,
> struct traceeval_type *type)
> {
> @@ -904,3 +904,256 @@ int traceeval_insert(struct traceeval *teval,
> else
> return update_entry(teval, entry, vals);
> }
> +
> +/**
> + * traceeval_iterator_put - release a given iterator
> + * @iter: The iterartor to release
> + *
> + * Frees the resources of an @iter that was created by
> + * traceeval_iterator_get().
> + */
> +void traceeval_iterator_put(struct traceeval_iterator *iter)
> +{
> + if (!iter)
> + return;
> +
> + free(iter->entries);
I think we also need to free **sort and *direction, which are both allocated
in traceeval_iterator_sort(). Probably need to update the function comment
as well to include allocs from that function.
> + free(iter);
> +}
<>
> +/**
> + * traceeval_iterator_sort - sort the entries that an iterator will return
> + * @iter: The iterator to specify the sort order of the entries
> + * @sort_field: The name of the key or value to sort with.
> + * @level: The level of sorting (0 for first order, 1 for second, ...)
> + * @ascending: If the sort should go forward or backward.
> + *
> + * The iterator has a list of entries to produce with traceeval_iterator_next().
> + * This function specifies what the order of the output of that function will
> + * be. Note, whenever this function is called, it resets the @iter so that
> + * the traceveal_iterator_next() will start from the beginning again.
> + *
> + * In other words, be very careful to ever call this function in a middle
> + * of a loop that is using traceeval_iterator_next(), otherwise you may end
> + * up in an infinite loop!
> + *
> + * The @level specifies the level of sorting. That is, for @level = 0,
> + * it will decide the main sorting of the @iter. For @level = 1, it will
> + * be the tie breaker for two entries that are equal for the @level = 0
> + * sort. @level = 2, will be the tie breaker for @level = 1, and so on.
> + *
> + * Note, if traceeval_iterator_next() is called, and there's a missing @level,
> + * it will fail. That is, if this function is called once with @level = 0 and
> + * againg with @level = 2, but never with @level = 1, the call to
> + * traceeval_iterator_next() will fail.
> + *
> + * If this function is called multiple times with the same @level, then the
> + * last call will define the what that @level will do.
> + *
> + * The @ascending will determine if "smaller" items go first if true, and
> + * "larger" items go first if false.
> + *
> + * Return 0 on success and -1 on failure.
> + */
> +int traceeval_iterator_sort(struct traceeval_iterator *iter, const char *sort_field,
> + int level, bool ascending)
> +{
> + bool *direction = iter->direction;
> + struct traceeval_type **sort = iter->sort;
> + struct traceeval_type *type;
> +
> + type = find_sort_type(iter->teval, sort_field);
> + if (!type)
> + return -1;
> +
> + /* pointer and dynamic types must have a cmp function */
> + switch (type->type) {
> + case TRACEEVAL_TYPE_POINTER:
> + case TRACEEVAL_TYPE_DYNAMIC:
> + if (!type->cmp)
> + return -1;
> + break;
> + default:
> + break;
> + }
> +
nit: It'd probably help with readability to have:
int num_levels = level + 1;
and use that instead of (level + 1).
> + if ((level + 1) > iter->nr_sort) {
> + sort = realloc(sort, sizeof(*sort) * (level + 1));
> + if (!sort)
> + return -1;
> +
> + iter->sort = sort;
> +
> + direction = realloc(direction, sizeof(*direction) * (level + 1));
> + if (!direction)
> + return -1;
> +
> + iter->direction = direction;
> +
> + /* Make sure the newly allocated contain NULL */
> + for (int i = iter->nr_sort; i < (level + 1); i++)
> + sort[i] = NULL;
> +
> + iter->nr_sort = level + 1;
> + }
> +
> + sort[level] = type;
> + direction[level] = ascending;
> + iter->needs_sort = true;
> + return 0;
> +}
<>
> +static int sort_iter(struct traceeval_iterator *iter)
> +{
> + int i;
> +
> + /* Make sure all levels are filled */
> + for (i = 0; i < iter->nr_sort; i++) {
> + if (!iter->sort[i])
> + return -1;
> + }
> +
> + qsort_r(iter->entries, iter->nr_entries, sizeof(*iter->entries),
> + iter_cmp, iter);
> +
> + iter->needs_sort = false;
> + iter->next = 0;
> +
> + return 0;
> +}
> +
> +/**
> + * traceeval_iterator_next - retrieve the next entry from an iterator
> + * @iter: The iterator to retrieve the next entry from
> + * @keys: The returned keys of the next entry (if exists)
> + *
> + * This returns the keys for the next entry in the traceeval being
> + * iterated over by @iter. If there are no more entries, 0 is returned
> + * and @keys are untouched.
> + *
> + * Returns 1 if another entry is returned, or 0 if not (or negative on error)
> + */
> +int traceeval_iterator_next(struct traceeval_iterator *iter,
> + const union traceeval_data **keys)
> +{
> + struct entry *entry;
> + int ret;
> +
> + if (iter->needs_sort) {
> + ret = sort_iter(iter);
> + if (ret < 0)
> + return ret;
> + iter->next = 0;
This is already done in sort_iter().
> + }
> +
> + if (iter->next >= iter->nr_entries)
> + return 0;
> +
> + entry = iter->entries[iter->next++];
> + *keys = entry->keys;
> + return 1;
> +}
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-08-16 21:36 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 5:39 [PATCH v2 00/17] libtraceeval histogram: Updates Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 01/17] libtraceeval histograms: Fix traceeval_results_release() error message Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 02/17] libtraceeval: Add sample task-eval program Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 03/17] libtraceeval hist: Add pointer and const string types Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 04/17] libtraceeval histogram: Have cmp and release functions be generic Steven Rostedt
2023-08-15 16:50 ` Ross Zwisler
2023-08-15 18:52 ` Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 05/17] libtraceeval histograms: Add traceeval struct to compare function Steven Rostedt
2023-08-15 16:55 ` Ross Zwisler
2023-08-15 18:53 ` Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 06/17] libtraceeval histogram: Remove comparing of traceeval and types Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 07/17] libtraceeval: Convert hist array into a hash table Steven Rostedt
2023-08-15 18:44 ` Ross Zwisler
2023-08-15 19:05 ` Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 08/17] libtraceeval histograms: Move hash functions into their own file Steven Rostedt
2023-08-15 19:31 ` Ross Zwisler
2023-08-15 20:23 ` Steven Rostedt
2023-08-15 22:56 ` Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 09/17] libtraceeval histogram: Label and check keys and values Steven Rostedt
2023-08-15 19:48 ` Ross Zwisler
2023-08-15 20:24 ` Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 10/17] libtraceeval histogram: Add updating of stats Steven Rostedt
2023-08-15 20:25 ` Ross Zwisler
2023-08-15 20:55 ` Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 11/17] libtraceeval histogram: Add iterator APIs Steven Rostedt
2023-08-16 21:34 ` Ross Zwisler [this message]
2023-08-16 21:49 ` Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 12/17] libtraceeval histogram: Add data copy callback Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 13/17] libtraceeval histogram: Do the release on updates Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 14/17] libtraceeval histogram: Use stack for old copy in update Steven Rostedt
2023-08-16 22:37 ` Ross Zwisler
2023-08-16 23:12 ` Steven Rostedt
2023-08-17 1:03 ` Steven Rostedt
2023-08-17 1:13 ` Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 15/17] libtraceeval histogram: Add traceeval_iterator_sort_custom() Steven Rostedt
2023-08-16 22:57 ` Ross Zwisler
2023-08-16 23:22 ` Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 16/17] libtraceeval histogram: Have traceeval_query() just give the pointer to results Steven Rostedt
2023-08-11 5:39 ` [PATCH v2 17/17] libtraceeval samples: Update task-eval to use the histogram logic 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=20230816213449.GA3686281@google.com \
--to=zwisler@google.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stevie.6strings@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.