All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Andi Kleen <ak@linux.intel.com>, Kan Liang <kan.liang@intel.com>,
	Dmitri Prokhorov <Dmitry.Prohorov@intel.com>,
	Valery Cherepennikov <valery.cherepennikov@intel.com>,
	Mark Rutland <mark.rutland@arm.com>,
	David Carrillo-Cisneros <davidcc@google.com>,
	Stephane Eranian <eranian@google.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/4]: perf/core: use rb trees for pinned/flexible groups
Date: Tue, 18 Jul 2017 16:38:48 +0300	[thread overview]
Message-ID: <b5d0c9e9-935f-ad3e-b917-e607752cdcc9@linux.intel.com> (raw)
In-Reply-To: <877ez6vtos.fsf@ashishki-desk.ger.corp.intel.com>

Hi,

On 18.07.2017 15:02, Alexander Shishkin wrote:
> Alexey Budankov <alexey.budankov@linux.intel.com> writes:
> 
>> +static void
>> +perf_event_groups_rotate(struct perf_event_groups *groups, int cpu)
>> +{
>> +	struct rb_node *node;
>> +	struct perf_event *node_event;
>> +
>> +	WARN_ON_ONCE(!groups);
> 
> This seems redundant.

Used that for debugging.

> 
>> +
>> +	list_rotate_left(&groups->list);
>> +
>> +	/* will replace rotation above in patch v5 3/4
>> +
>> +	node = groups->tree.rb_node;
>> +
>> +	while (node) {
>> +		node_event = container_of(node,
>> +				struct perf_event, group_node);
>> +
>> +		if (cpu < node_event->cpu) {
>> +			node = node->rb_left;
>> +		} else if (cpu > node_event->cpu) {
>> +			node = node->rb_right;
>> +		} else {
>> +			list_rotate_left(&node_event->group_list);
>> +			break;
>> +		}
>> +	}
>> +
>> +	*/
> 
> Please don't do this, it doesn't add clarity.

Accepted. Put it here just for review process simplification.

> 
>> +static int
>> +perf_event_groups_iterate(struct perf_event_groups *groups,
>> +		perf_event_groups_iterate_f callback, void *data)
>> +{
>> +	int ret = 0;
>> +	struct perf_event *event;
>> +
>> +	WARN_ON_ONCE(!groups);
>> +
>> +	list_for_each_entry(event, &groups->list, group_list_entry) {
>> +		ret = callback(event, data);
>> +		if (ret)
>> +			break;
>> +	}
>> +
>> +	/* will replace itration above in patch v5 4/4
>> +
>> +	for (node = rb_first(groups); node; node = rb_next(node)) {
>> +		node_event = container_of(node,	struct perf_event, group_node);
>> +		list_for_each_entry(event, &node_event->group_list,
>> +				group_list_entry) {
>> +			WARN_ON_ONCE(!(event->cpu == node_event->cpu));
>> +			ret = callback(event, data);
>> +			if (ret) {
>> +				return ret;
>> +			}
>> +		}
>> +	}
>> +
>> +	*/
> 
> Ditto.
> 
> Regards,
> --
> Alex
> 

Thanks,
Alexey

  reply	other threads:[~2017-07-18 13:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 13:03 [PATCH v5 1/4]: perf/core: use rb trees for pinned/flexible groups Alexey Budankov
2017-07-18 12:02 ` Alexander Shishkin
2017-07-18 13:38   ` Alexey Budankov [this message]
2017-07-18 12:29 ` Alexander Shishkin
2017-07-18 13:39   ` Alexey Budankov
2017-07-19  6:36     ` Alexander Shishkin

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=b5d0c9e9-935f-ad3e-b917-e607752cdcc9@linux.intel.com \
    --to=alexey.budankov@linux.intel.com \
    --cc=Dmitry.Prohorov@intel.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=davidcc@google.com \
    --cc=eranian@google.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=valery.cherepennikov@intel.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.