All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirill Batuzov <batuzovk@ispras.ru>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Speedup 'tb_find_slow' by using the same heuristic as during memory page lookup
Date: Sun, 05 Dec 2010 10:14:44 +0300	[thread overview]
Message-ID: <4CFB3BE4.1090505@ispras.ru> (raw)
In-Reply-To: <AANLkTi=COsAhoMAOvUBAaXC86_JP4y6MvJ9onPSi3TiY@mail.gmail.com>

On 04.12.2010 23:11, Blue Swirl wrote:
> On Thu, Dec 2, 2010 at 1:12 PM, Kirill Batuzov<batuzovk@ispras.ru>  wrote:
>> Move the last found TB to the head of the list so it will be found more quickly next time it will be looked for.
>>
>> Signed-off-by: Kirill Batuzov<batuzovk@ispras.ru>
>> Signed-off-by: Pavel Yushchenko<pau@ispras.ru>
>> ---
>>
>> This patch appeared during investigation of performance issues with
>> S5PC110 emulation for Samsung. It increses OS startup speed significantly.
>
> The patch looks reasonable, but I didn't see any visible difference in
> my tests. Could you report your numbers?

The exact numbers depend on complexity of guest system.
  - For basic Debian system (no X-server) on versatilepb we observed 25% 
decrease of boot time.
  - For to-be released Samsung LIMO platform on S5PC110 board we 
observed 2x (for older version) and 3x (for newer version) decrease of 
boot time.
  - Small CPU-intensive benchmarks are not affected because they are 
completely handled by 'tb_find_fast'.

We also noticed better response time for heavyweight GUI applications, 
but I do not know how to measure it accurately.

----
   Kirill.

  reply	other threads:[~2010-12-05  7:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 13:12 [Qemu-devel] [PATCH] Speedup 'tb_find_slow' by using the same heuristic as during memory page lookup Kirill Batuzov
2010-12-04 20:11 ` Blue Swirl
2010-12-05  7:14   ` Kirill Batuzov [this message]
2010-12-05  8:22     ` Blue Swirl

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=4CFB3BE4.1090505@ispras.ru \
    --to=batuzovk@ispras.ru \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.