All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 18/18] libtraceeval: Add traceeval_remove()
Date: Thu, 17 Aug 2023 14:12:03 -0600	[thread overview]
Message-ID: <20230817201203.GC73817@google.com> (raw)
In-Reply-To: <20230817013310.88582-19-rostedt@goodmis.org>

On Wed, Aug 16, 2023 at 09:33:10PM -0400, Steven Rostedt wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
> 
> Add a way to remove an entry that's in the traceeval. Currently there's
> only ways to add entries, but there also needs to be a way to remove them
> too.
> 
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
>  include/traceeval-hist.h |  3 +++
>  src/histograms.c         | 29 +++++++++++++++++++++++++++++
>  2 files changed, 32 insertions(+)
> 
> diff --git a/include/traceeval-hist.h b/include/traceeval-hist.h
> index 37147d626fbb..8e5a6451f399 100644
> --- a/include/traceeval-hist.h
> +++ b/include/traceeval-hist.h
> @@ -160,6 +160,9 @@ int traceeval_insert(struct traceeval *teval,
>  		     const union traceeval_data *keys,
>  		     const union traceeval_data *vals);
>  
> +int traceeval_remove(struct traceeval *teval,
> +		     const union traceeval_data *keys);
> +
>  int traceeval_query(struct traceeval *teval, const union traceeval_data *keys,
>  		    const union traceeval_data **results);
>  
> diff --git a/src/histograms.c b/src/histograms.c
> index c16b8866b84a..f35d1b2e583d 100644
> --- a/src/histograms.c
> +++ b/src/histograms.c
> @@ -934,6 +934,35 @@ int traceeval_insert(struct traceeval *teval,
>  		return update_entry(teval, entry, vals);
>  }
>  
> +/**
> + * traceeval_remove - remove an item from the traceeval descriptor
> + * @teval: The descriptor to insert into
                                remove from

Aside from that one nit you can add:

Reviewed-by: Ross Zwisler <zwisler@google.com>

> + * @keys: The list of keys that defines what is being removed
> + *
> + * This is the opposite of traceeval_insert(). Instead of inserting
> + * an item into the traceeval historgram, it removes it.
> + *
> + * Returns 1 if it found and removed an item,
> + *         0 if it did not find an time matching @keys
> + *        -1 if there was an error.
> + */
> +int traceeval_remove(struct traceeval *teval,
> +		     const union traceeval_data *keys)
> +{
> +	struct hash_table *hist = teval->hist;
> +	struct entry *entry;
> +	int check;
> +
> +	entry = NULL;
> +	check = get_entry(teval, keys, &entry);
> +
> +	if (check < 1)
> +		return check;
> +
> +	hash_remove(hist, &entry->hash);
> +	return 1;
> +}
> +
>  /**
>   * traceeval_iterator_put - release a given iterator
>   * @iter: The iterartor to release
> -- 
> 2.40.1
> 

  reply	other threads:[~2023-08-17 20:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17  1:32 [PATCH v3 00/18] libtraceeval histogram: Updates Steven Rostedt
2023-08-17  1:32 ` [PATCH v3 01/18] libtraceeval histograms: Fix traceeval_results_release() error message Steven Rostedt
2023-08-17  1:32 ` [PATCH v3 02/18] libtraceeval: Add sample task-eval program Steven Rostedt
2023-08-17  1:32 ` [PATCH v3 03/18] libtraceeval hist: Add pointer and const string types Steven Rostedt
2023-08-17  1:32 ` [PATCH v3 04/18] libtraceeval histogram: Have cmp and release functions be generic Steven Rostedt
2023-08-17  1:32 ` [PATCH v3 05/18] libtraceeval histograms: Add traceeval struct to compare function Steven Rostedt
2023-08-17  1:32 ` [PATCH v3 06/18] libtraceeval histogram: Remove comparing of traceeval and types Steven Rostedt
2023-08-17  1:32 ` [PATCH v3 07/18] libtraceeval: Convert hist array into a hash table Steven Rostedt
2023-08-17  1:33 ` [PATCH v3 08/18] libtraceeval histograms: Move hash functions into their own file Steven Rostedt
2023-08-17  1:33 ` [PATCH v3 09/18] libtraceeval histogram: Label and check keys and values Steven Rostedt
2023-08-17  1:33 ` [PATCH v3 10/18] libtraceeval histogram: Add updating of stats Steven Rostedt
2023-08-17  1:33 ` [PATCH v3 11/18] libtraceeval histogram: Add iterator APIs Steven Rostedt
2023-08-17  1:33 ` [PATCH v3 12/18] libtraceeval histogram: Add data copy callback Steven Rostedt
2023-08-17  1:33 ` [PATCH v3 13/18] libtraceeval histogram: Do the release on updates Steven Rostedt
2023-08-17  1:33 ` [PATCH v3 14/18] libtraceeval histogram: Use stack for old copy in update Steven Rostedt
2023-08-17 19:29   ` Ross Zwisler
2023-08-17 19:42     ` Steven Rostedt
2023-08-17 19:44       ` Ross Zwisler
2023-08-17 20:25         ` Steven Rostedt
2023-08-17  1:33 ` [PATCH v3 15/18] libtraceeval histogram: Add traceeval_iterator_sort_custom() Steven Rostedt
2023-08-17  1:33 ` [PATCH v3 16/18] libtraceeval histogram: Have traceeval_query() just give the pointer to results Steven Rostedt
2023-08-17  1:33 ` [PATCH v3 17/18] libtraceeval samples: Update task-eval to use the histogram logic Steven Rostedt
2023-08-17  1:33 ` [PATCH v3 18/18] libtraceeval: Add traceeval_remove() Steven Rostedt
2023-08-17 20:12   ` Ross Zwisler [this message]
2023-08-17  1:35 ` [PATCH v3 00/18] libtraceeval histogram: Updates Steven Rostedt
2023-08-17 20:13 ` Ross Zwisler
2023-08-17 20:31   ` Steven Rostedt
2023-08-17 20:37     ` 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=20230817201203.GC73817@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.