Salman <sqazi@google.com> writes:
quoted text
> +
> +static int proc_stats(struct ctl_table *table, int write,
> +		      void __user *buffer, size_t *lenp, loff_t *ppos)
> +{
> +	int ret;
> +	unsigned long stats[3];
> +	int cpu = (int)((long)table->extra1);
> +	struct ctl_table fake = {};
> +
> +	if (write)
> +		return -EINVAL;
> +
> +	fake.data = stats;
> +	fake.maxlen = 3*sizeof(unsigned long);
> +
> +	ret = smp_call_function_single(cpu, getstats, &stats, 1);
> +	if (ret)
> +		return ret;

Haven't read the whole thing, but do any of these stats really
need to execute on the target CPU? They seem to be just readable
fields.

Or does it simply not matter because this proc call is too infrequent?

Anyways global broadcasts are discouraged, there is typically
always someone who feels their RT latency be messed up by them.

-Andi


-- 
ak@linux.intel.com -- Speaking for myself only.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/