All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Performance disparity, problem found
Date: Thu, 01 Apr 2010 14:50:58 +0100	[thread overview]
Message-ID: <4BB4A4C2.4090901@grupopie.com> (raw)
In-Reply-To: <201004011430.56503.elendil@planet.nl>

Frans Pop wrote:
> Paulo Marques wrote:
>> Now the problem is that /proc/cpuinfo is read only. Would it be possible
>> to make /proc/cpuinfo writable so that I could do:
>>
>> echo -n "model name      : Intel(R) Core(TM)2 Quad CPU    Q6600  @
>> 2.40GHz" > /proc/cpuinfo
>>
>> in the first machine and get a performance similar to the second machine?
> 
> Good catch! 'chmod +w /proc/cpuinfo' should do the trick.
> 
> Cheers,
> FJP

Thanks, that did the trick. My first machine is much faster now and it
even has 4 cores! :)

-- 
Paulo Marques - www.grupopie.com

"All I ask is a chance to prove that money can't make me happy."

      reply	other threads:[~2010-04-01 13:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 11:30 Performance disparity, problem found Paulo Marques
2010-04-01 12:30 ` Frans Pop
2010-04-01 13:50   ` Paulo Marques [this message]

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=4BB4A4C2.4090901@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@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 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.