> > From: Dave Airlie <airl...@redhat.com> > > > > This avoids needing to do a kmalloc > PAGE_SIZE for the main > > indirect buffer chunk, it adds an accessor for all reads from > > the chunk and caches a single page at a time for subsequent > > reads. > > FWIW, this works on my PowerBook but seems to drop x11perf -aa10text > numbers from about 370k/s to about 315k/s.
Yeah I'm unsure how to bring back up the speed, two ideas I have are: 1) won't help you but on PCI/PCIE we can use the IB to read from and avoid copying the chunk since its all cache coherent 2) keep a bitmap of the pages, copy to the kpage and then to IB, then the IB copy from user can just copy any pages we don't hit. But since what we are doing now is inherently broken, getting order 5 pages once the system is running is not something we'd expect to work. I expect this solution is still faster than the vmalloc overhead. Dave. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
