[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53ADF8FC.5030604@gmail.com>
Date: Fri, 27 Jun 2014 17:06:36 -0600
From: David Ahern <dsahern@...il.com>
To: Jiri Olsa <jolsa@...nel.org>, linux-kernel@...r.kernel.org
CC: Arnaldo Carvalho de Melo <acme@...nel.org>,
Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Jean Pihet <jean.pihet@...aro.org>,
Namhyung Kim <namhyung@...nel.org>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH 05/18] perf tools: Add ordered_events_(get|put) interface
On 6/18/14, 8:58 AM, Jiri Olsa wrote:
>
> +static struct ordered_event*
> +ordered_events_get(struct ordered_events_queue *q, u64 timestamp)
> +{
> + struct ordered_event *new;
> +
> + new = alloc_event(q);
> + if (new) {
> + new->timestamp = timestamp;
> + queue_event(q, new);
> + }
> +
> + return new;
> +}
The _get name does not really correlate with what is happening -- ie.,
allocate a new event and add it to the queue. There is no reference
taken either.
> +
> +static void
> +ordered_event_put(struct ordered_events_queue *q, struct ordered_event *iter)
> +{
> + list_del(&iter->list);
> + list_add(&iter->list, &q->cache);
> + q->nr_events--;
> +}
Similarly here with the _put. In this case the function is moving the
event from one list to another. And how about something else for the
name besides iter -- oe, or oevent?
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists