How to disable slow agpgart in kernel config?
Quoted 8 lines
Quoted 4 lines
This surprises me, especially considering the in-kernel nvidia-agp driver was actually written by NVidia. Are there any agp error messages in your dmesg / X log ?
With the nVidia own
nv_agpit appears directly in all apps, very fast under GNOME 2.8.1. Why, I do not know. Also game (opengl) performance is faster with thenv_agp, that I haven't used the kernel agp for months, now.
This is interesting. I always used agpgart without a second thought (2.4.29, GeForce4 MX with Via KT133 chipset).
I just read through the nVidia readme file, and there is a comprehensive section on what module to use for what chipset (and card). It recommends using the nVagp for my setup, so I just rebuilt excluding agpgart so I can use the nVdia module.
I never had slowness as such in KDE or X apps, but playing quake2 openGL I used to get a 'wave' type effect rippling down the screen occasionally. A quick test using the nVagp module to have fixed that...
I will test for a few weeks.
Nick
Signature · 2 lines
"When you're chewing on life's gristle, Don't grumble, Give a whistle..."
Quoted 11 lines · Nick Warne
Quoted 7 lines
Quoted 3 lines
This surprises me, especially considering the in-kernel nvidia-agp driver was actually written by NVidia. Are there any agp error messages in your dmesg / X log ?
With the nVidia own
nv_agpit appears directly in all apps, very fast under GNOME 2.8.1. Why, I do not know. Also game (opengl) performance is faster with thenv_agp, that I haven't used the kernel agp for months, now.This is interesting. I always used agpgart without a second thought (2.4.29, GeForce4 MX with Via KT133 chipset).
Quoted 8 lines
I just read through the nVidia readme file, and there is a comprehensive section on what module to use for what chipset (and card). It recommends using the nVagp for my setup, so I just rebuilt excluding agpgart so I can use the nVdia module.
I never had slowness as such in KDE or X apps, but playing quake2 openGL I used to get a 'wave' type effect rippling down the screen occasionally. A quick test using the nVagp module to have fixed that...
Terrence, any ideas ?
The only thing that jumps to mind that the nvidia gart driver is doing that the opensource one isn't is fiddling with PAT bits in the GART pages, but if anything, that should be just a performance thing.
(It'd be really nice to get your PAT support in 2.6 sometime too btw).
Dave
Quoted 18 lines · On Fri, Feb 11, 2005 at 01:48:21PM -0500, [email protected] wrote:
Quoted 16 lines · Nick Warne
Quoted 7 lines
Quoted 3 lines
This surprises me, especially considering the in-kernel nvidia-agp driver was actually written by NVidia. Are there any agp error messages in your dmesg / X log ?
With the nVidia own
nv_agpit appears directly in all apps, very fast under GNOME 2.8.1. Why, I do not know. Also game (opengl) performance is faster with thenv_agp, that I haven't used the kernel agp for months, now.This is interesting. I always used agpgart without a second thought (2.4.29, GeForce4 MX with Via KT133 chipset).
I just read through the nVidia readme file, and there is a comprehensive section on what module to use for what chipset (and card). It recommends using the nVagp for my setup, so I just rebuilt excluding agpgart so I can use the nVdia module.
Quoted 5 lines
Quoted 3 lines
I never had slowness as such in KDE or X apps, but playing quake2 openGL I used to get a 'wave' type effect rippling down the screen occasionally. A quick test using the nVagp module to have fixed that...
Terrence, any ideas ?
I would agree with your assessment Dave, there's very little difference betweeen the agp drivers. it's possible nvagp tweaks some register values that agpgart doesn't, I'd have to look closer at both to know. that might explain *modest* performance differences, but certainly wouldn't explain the dramatic performance differences the original poster described.
I wouldn't expect even falling back to pci dma would have this big of an impact on 2d performance, but perhaps there's enough bus activity for this to happen. Marcus, can you verify that you're actually using agpgart in that situation? do you possibly have our XF86Config option set to nvagp only? (with IOMMU compiled in or agpgart loaded, our driver won't allow nvagp) you can verify whether agp is enabled with this command when our driver is loaded and X is started up:
% cat /proc/drivers/nvidia/agp/status
Status: Disabled
(hmm, turns out my own dev machine doesn't have agp enabled and 2d performance isn't very noticeable)
Quoted 3 lines
Quoted 3 lines
I just read through the nVidia readme file, and there is a comprehensive section on what module to use for what chipset (and card). It recommends using the nVagp for my setup,
is that the "CONFIGURING AGP" appendix? I didn't think that we recommended which agp driver to use. the intention was just to document which chipsets are supported by nvagp and point out that agpgart may/probably supports more chipsets. that section also documents some hardware 'issues' that we work around. we work around these issues regardless of which agp driver is being used.
for this via kt133 issue, I looked through the agpgart and nvagp initializations and didn't see anything much different. both initialize and flush gart mappings the same way. both seem to allocate memory the same way (nvagp uses __get_free_pages, which eventually calls alloc_pages) with the GFP_KERNEL flag. I'm not sure why there would be much difference between the two.
Quoted 1 line
(It'd be really nice to get your PAT support in 2.6 sometime too btw).
I've been meaning to finish that up. the actual PAT support is pretty simple; it's the protecting against cache aliasing that's a bit tricky and involved. for our push buffers, we don't worry too much about the cache aliasing, since change_page_attr() marks the kernel mapping uncached, and there shouldn't be any other mappings to the memory. mapping i/o regions like the framebuffer is a bit riskier, since it's more likely someone else has a conflicting mapping to it, but the damage of data corruption is much less fatal.
Thanks,
Terence
Quoted 10 lines · Terence Ripperda
Quoted 3 lines
Quoted 3 lines
I just read through the nVidia readme file, and there is a comprehensive section on what module to use for what chipset (and card). It recommends using the nVagp for my setup,
is that the "CONFIGURING AGP" appendix? I didn't think that we recommended which agp driver to use. the intention was just to document which chipsets are supported by nvagp and point out that agpgart may/probably supports more chipsets. that section also documents some hardware 'issues' that we work around. we work around these issues regardless of which agp driver is being used.
Thats the one. I read this in APPENDIX F:
"The following AGP chipsets are supported by NVIDIA's AGP; for all other chipsets it is recommended that you use the AGPGART module."
as saying 'if you have one of these chipsets use nVagp' else use agpgart.
Quoted 6 lines
for this via kt133 issue, I looked through the agpgart and nvagp initializations and didn't see anything much different. both initialize and flush gart mappings the same way. both seem to allocate memory the same way (nvagp uses
__get_free_pages, which eventually callsalloc_pages) with theGFP_KERNELflag. I'm not sure why there would be much difference between the two.
I have had no issue at all running agpgart on Slackware 10 with KDE 3.3.x. It was just when I read this thread I didn't realise there was another option of a different NV module. I just tried it after reading deeper in the readme.txt ref. the Quake2 OpenGL 'rippling wave' I get every 5 minutes or so. It fixed it, BTW. I now have a constant clear display 100% in Quake2 :) I haven't noticed any difference at all in 2d desktop stuff (except maybe it is slightly brighter).
Nick
Signature · 2 lines
"When you're chewing on life's gristle, Don't grumble, Give a whistle..."