From: Dave Jones <davej@redhat.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Matt Mackall <mpm@selenic.com>, linux-kernel@vger.kernel.org
Subject: Re: [POLL] SLAB : Are the 32 and 192 bytes caches really usefull on x86_64 machines ?
Date: Wed, 4 Jan 2006 00:26:35 -0500 [thread overview]
Message-ID: <20060104052635.GA5558@redhat.com> (raw)
In-Reply-To: <23471.1135821010@ocs3.ocs.com.au>
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.
I looked at this a little closer. If my understanding of the console/fb layers
is correct, soft_cursor() is serialised by the console_sem in
drivers/video/console/fbcon.c::fb_flashcursor()
Dave
next prev parent reply other threads:[~2006-01-04 5:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 8:00 [ANNOUNCE] GIT 1.0.0 Junio C Hamano
2005-12-21 9:11 ` [POLL] SLAB : Are the 32 and 192 bytes caches really usefull on x86_64 machines ? Eric Dumazet
2005-12-21 9:22 ` David S. Miller
2005-12-21 10:03 ` Jan-Benedict Glaw
2005-12-21 9:46 ` Alok kataria
2005-12-21 12:44 ` Ed Tomlinson
2005-12-21 13:20 ` Folkert van Heusden
2005-12-21 13:38 ` Eric Dumazet
2005-12-21 14:09 ` Folkert van Heusden
2005-12-21 16:40 ` Dave Jones
2005-12-21 19:36 ` Folkert van Heusden
2005-12-28 8:32 ` Denis Vlasenko
2005-12-28 8:54 ` Denis Vlasenko
2005-12-28 17:57 ` Andreas Kleen
2005-12-28 21:01 ` Matt Mackall
2005-12-29 1:26 ` Dave Jones
2005-12-30 4:06 ` Steven Rostedt
2006-01-02 8:46 ` Pekka Enberg
2006-01-02 8:51 ` Pekka Enberg
2006-01-02 12:33 ` Steven Rostedt
2006-01-02 12:31 ` Steven Rostedt
2005-12-29 1:29 ` Dave Jones
2005-12-29 1:50 ` Keith Owens
2005-12-29 2:39 ` Dave Jones
2006-01-02 15:03 ` Helge Hafting
2006-01-04 5:26 ` Dave Jones [this message]
2005-12-30 21:13 ` Marcelo Tosatti
2005-12-31 20:13 ` Andi Kleen
2005-12-29 19:48 ` Steven Rostedt
2005-12-29 21:16 ` Andi Kleen
2006-01-02 8:37 ` Pekka Enberg
2006-01-02 12:45 ` Andi Kleen
2006-01-02 13:04 ` Pekka J Enberg
2006-01-02 13:56 ` Andi Kleen
2006-01-02 15:09 ` Pekka J Enberg
2006-01-02 15:46 ` Jörn Engel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060104052635.GA5558@redhat.com \
--to=davej@redhat.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox