Messages in this thread | | | Date | Tue, 16 Dec 2003 22:46:12 -0800 (PST) | From | Linus Torvalds <> | Subject | Re: PCI Express support for 2.4 kernel |
| |
On Wed, 17 Dec 2003, Vladimir Kondratiev wrote: > > Hopefully, they (or we, should I count myself?) are not completely brain > dead. Old method still works.
Good. I just wanted to check from a timing perspective - it means that this won't be an issue for most people for a while (ie until we start seeing actual PCI-X-specific hardware and drivers rather than just the support chipsets - and I obviously have no idea how long that will take)
So if this will only matter for PCI-X drivers and not for discovery etc, I wonder if it wouldn't make sense to have this as a totally separate function? Instead of trying to make the existing "pci_config_xxxx()" stuff work with PCI-X, wouldn't it be nicer to have the driver just map its config space on probe?
That way there would be no scalability issues (only as many pages mapped as there are actual physical PCI-X devices that care) _and_ there would be no performance issues (the users would not need to walk page tables or flush the TLB - they'd just have a direct-mapped pointer).
You could do it with just ioremap(), but you'd really want to abstract it out a bit, and have a "[un]map_pcix_config()" function?
Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |