Re: [POLL] SLAB : Are the 32 and 192 bytes caches really usefull on x86_64 machines ?

[Helge Hafting <helgehaf@aitel.hist.no>]

On Wed, Dec 28, 2005 at 09:39:06PM -0500, Dave Jones wrote:
> On Thu, Dec 29, 2005 at 12:50:10PM +1100, Keith Owens wrote:
>  > Dave Jones (on Wed, 28 Dec 2005 20:29:15 -0500) wrote:
>  > >
>  > > > Something like this:
>  > > > 
>  > > > http://lwn.net/Articles/124374/
>  > >
>  > >One thing that really sticks out like a sore thumb is soft_cursor()
>  > >That thing gets called a *lot*, and every time it does a kmalloc/free
>  > >pair that 99.9% of the time is going to be the same size alloc as
>  > >it was the last time.  This patch makes that alloc persistent
>  > >(and does a realloc if the size changes).
>  > >The only time it should change is if the font/resolution changes I think.
>  > 
>  > Can soft_cursor() be called from multiple processes at the same time,
>  > in particular with dual head systems?  If so then a static variable is
>  > not going to work.
> 
> My dual-head system here displays a cloned image on the second
> screen, which seems to dtrt.  I'm not sure how to make it show
> something different on the other head to test further.

Few dualhead drivers actually support two different framebuffers,
but the matrox G550 (and G400) drivers do.  Compile one
of those, make sure to configure dualhead support.
After booting up, use "matroxset" to set the 
framebuffer to vga-connector mapping so that the two 
outputs actually show the different framebuffers.

Another way is to use several graphichs cards (AGP getting
the first framebuffer and each PCI card getting others as
the drivers load.)

Helge Hafting
-
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/