Have you tried reading the documentation on your North Bridge chip ? This
may change from chip to chip, depending on how it partitions resources
between the agp and the pci buses. Also, if you have access to it, an
oscilloscope will come in handy to figure out what’s going on, you can try
playing music while running a high-bandwidth video benchmark (such as
Viewperf), or run some high bandwith game with sound on.
Alberto.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Mark Knutson
Sent: Tuesday, July 13, 2004 8:58 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] AGP latency setting impacts other PCI bus devices–but
why?
I developed a program that allows adjustment of the pci latency setting of
the agp video card for the benefit of those using their pc for making music.
Reducing the agp latency setting from 248 to 128 often is a big help for the
pci sound card.
The problem I have is I don’t have a specific idea of why this should be. I
note that the agp bus is electrically distinct from the PCI bus that
contains the sound card, and the agp has its own direct path into memory and
so forth. Agp does, of course, expose some of the PCI configuration
settings such as that of the latency timer at 0x0d into the configuration
header.
So I can speculate that when the agp bus is going balls-out transferring
data using its high-bandwidth technology, that devices on other PCI devices
are somewhow prevented from acquiring some shared resource. Thing is, I
wish I had more specific knowledge of the exact nature of this performance
contention.
If anybody can help, it is greatly appreciated. I have the Shanley book on
PCI, but it explains the workings of individual devices on a shared bus and
I can’t find a reason why two busses would have contention–memory access
would be the number one suspect.
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.