mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Arjan van de Ven <arjan@linux.intel.com>,
	Senthil Balasubramanian <senthilkumar@atheros.com>,
	Aeolus Yang <Aeolus.Yang@atheros.com>,
	Jonathan May <Jonathan.May@atheros.com>
Cc: Thomas Renninger <trenn@suse.de>,
	davej@redhat.com, cpufreq@vger.kernel.org,
	linux-kernel@vger.kernel.org, Matthew Garrett <mjg@redhat.com>,
	Reinette Chatre <reinette.chatre@intel.com>,
	Amod Bodas <Amod.Bodas@atheros.com>,
	David Quan <David.Quan@atheros.com>,
	Kishore Jotwani <Kishore.Jotwani@atheros.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cpu-freq: add troubleshooting section for FSB changes
Date: Mon, 9 Nov 2009 08:32:43 -0800	[thread overview]
Message-ID: <43e72e890911090832v1c809482yde7e767502271376@mail.gmail.com> (raw)
In-Reply-To: <4AF5FBC7.9000105@linux.intel.com>

On Sat, Nov 7, 2009 at 2:59 PM, Arjan van de Ven <arjan@linux.intel.com> wrote:
>>> 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.
>>
>> So when should people look at this?
>
> at this point the atheros folks haven't even confirmed that this is the
> cause...

And we tested this (reducing the min cpu freq to one less than the
highest supported P state to avoid an FSB speed change) and it seems
doing the steps described here did not fix the issue. But at least now
if anyone else wants to verify this they can with some sort of
documentaiton.

So to confirm though -- we are seeing a huge performance depredation
mainly on RX on an Intel Pine Trail platform with SpeedStep enabled on
the BIOS.

Let me get into the specifics in case anyone is able to help. The
issue is with ath9k on RX and the CPU on C3 state requesting DMA over
PCI-E. We typically would get about 110 Mbps with an AR9285 (single
stream) but when SpeedStep is enabled it goes down to 25 Mbps. At the
PCI-E level we are seeing huge latencies introduced when SpeedStep is
used for DMA requests to the Intel root complex on the Intel Pine
trail platform. Latencies are about 20-60 us.

Is there a timeout threshold change that will cause the Intel chipset
wait for some time after completion before going into a C3 state? Are
there any other explanations for seeing such huge latencies on C3
state?

Thanks for your review and help with this. Any suggestions are greatly
appreciated.

  Luis

  parent reply	other threads:[~2009-11-09 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 20:01 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
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 [this message]
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=43e72e890911090832v1c809482yde7e767502271376@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=Aeolus.Yang@atheros.com \
    --cc=Amod.Bodas@atheros.com \
    --cc=David.Quan@atheros.com \
    --cc=Jonathan.May@atheros.com \
    --cc=Kishore.Jotwani@atheros.com \
    --cc=arjan@linux.intel.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=reinette.chatre@intel.com \
    --cc=senthilkumar@atheros.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

all inboxes | Powered by JetHome®