public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] - Speed up boot - skip unnecessary clock calibration
Date: Tue, 27 Mar 2007 17:53:10 +0000	[thread overview]
Message-ID: <20070327175309.GE15035@parisc-linux.org> (raw)
In-Reply-To: <20070327132953.GA14401@sgi.com>

On Tue, Mar 27, 2007 at 08:29:54AM -0500, Jack Steiner wrote:
> +	if (local_cpu_data->itc_freq != per_cpu(cpu_info, cpuid - 1).itc_freq ||
> +			local_cpu_data->proc_freq != per_cpu(cpu_info, cpuid - 1).proc_freq ||
> +	    		local_cpu_data->features != per_cpu(cpu_info, cpuid - 1).features ||
> +	    		local_cpu_data->revision != per_cpu(cpu_info, cpuid - 1).revision ||
> +	    		local_cpu_data->family != per_cpu(cpu_info, cpuid - 1).family ||
> +	    		local_cpu_data->archrev != per_cpu(cpu_info, cpuid - 1).archrev ||
> +	    		local_cpu_data->model != per_cpu(cpu_info, cpuid - 1).model)
> +		calibrate_delay();

If you use a temporary variable, you improve speed a little, and you
don't exceed 80 columns:

+	struct cpuinfo_ia64 *last_cpu_info = cpu_data(cpuid - 1);
+	struct cpuinfo_ia64 *this_cpu_info = local_cpu_data;
+	if (last_cpu_info->itc_freq != this_cpu_info->itc_freq ||
+	    last_cpu_info->proc_freq != this_cpu_info->proc_freq ||
+	    last_cpu_info->features != this_cpu_info->features ||
+	    last_cpu_info->revision != this_cpu_info->revision ||
+	    last_cpu_info->family != this_cpu_info->family ||
+	    last_cpu_info->archrev != this_cpu_info->archrev ||
+	    last_cpu_info->model != this_cpu_info->model)
+		calibrate_delay();


  reply	other threads:[~2007-03-27 17:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 13:29 [PATCH] - Speed up boot - skip unnecessary clock calibration Jack Steiner
2007-03-27 17:53 ` Matthew Wilcox [this message]
2007-03-27 18:42 ` Luck, Tony
2007-03-27 19:17 ` Yu, Fenghua
2007-03-27 19:22 ` Jack Steiner
2007-03-27 19:30 ` Jack Steiner

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=20070327175309.GE15035@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=linux-ia64@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox