From: Arjan van de Ven <arjan@linux.intel.com>
To: Thomas Renninger <trenn@suse.de>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
davej@redhat.com, cpufreq@vger.kernel.org,
linux-kernel@vger.kernel.org, mcgrof@gmail.com,
Matthew Garrett <mjg@redhat.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Aeolus Yang <Aeolus.Yang@atheros.com>,
Amod Bodas <Amod.Bodas@atheros.com>,
David Quan <David.Quan@atheros.com>,
Kishore Jotwani <Kishore.Jotwani@atheros.com>
Subject: Re: [PATCH] cpu-freq: add troubleshooting section for FSB changes
Date: Sat, 07 Nov 2009 16:28:12 -0600 [thread overview]
Message-ID: <4AF5F47C.5000402@linux.intel.com> (raw)
In-Reply-To: <200911072152.57596.trenn@suse.de>
Thomas Renninger wrote:
[please cut away the part of the mail you're not responding to; your mail was 90% like that]
> On Friday 06 November 2009 09:01:00 pm Luis R. Rodriguez wrote:
>> With cpu frequency scaling you may run into some system
>> performance issues when the FSB changes speed due to the
>> throughput constraints this brings on the system.
> Interesting.
> Could you be a bit more detailed how and what kind of perfomance issues are
> seen, please.
> I expect IO based issues like WLAN package throughput or even lost connections :)
the bus doesn't get THAT slow.....
in addition, most FSB systems have the memory controller in the chipset, next to the PCI
logic... so that the FSB bus for DMA transactions only carries the snoop traffic, not the whole data.
next prev parent reply other threads:[~2009-11-07 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 20:01 [PATCH] cpu-freq: add troubleshooting section for FSB changes Luis R. Rodriguez
2009-11-07 20:52 ` Thomas Renninger
2009-11-07 21:10 ` Thomas Renninger
2009-11-07 22:28 ` Arjan van de Ven [this message]
2009-11-07 22:47 ` Thomas Renninger
2009-11-07 22:59 ` Arjan van de Ven
2009-11-08 0:54 ` Matthew Garrett
2009-11-09 16:32 ` Luis R. Rodriguez
2009-11-10 12:12 ` Corrado Zoccolo
2009-11-13 17:18 ` Luis R. Rodriguez
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=4AF5F47C.5000402@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=Aeolus.Yang@atheros.com \
--cc=Amod.Bodas@atheros.com \
--cc=David.Quan@atheros.com \
--cc=Kishore.Jotwani@atheros.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mcgrof@gmail.com \
--cc=mjg@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=trenn@suse.de \
/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