From: "Jan Beulich" <jbeulich@novell.com>
To: xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>
Subject: Re: early_cpu_init() and identify_cpu()
Date: Tue, 17 Jul 2007 10:58:39 +0100 [thread overview]
Message-ID: <469CAEEF.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C2C23340.128BC%keir@xensource.com>
>>> Keir Fraser <keir@xensource.com> 17.07.07 09:50 >>>
>On 16/7/07 09:18, "Jan Beulich" <jbeulich@novell.com> wrote:
>
>>> How much faster is scrolling of WC framebuffer on your test system?
>>
>> That's a win of about 30%, and using movsq in memcpy() is another win of
>> about 50%. Will probably create a vidmemmove()...
>
>That still totally sucks then. Paging a full screen of text of, say 60
>lines, done line-by-line will still take, say 60*300ms == 20 seconds(ish).
No, you got me wrong - with 'scrolling by one line' I mean the scrolling the
entire screen up by a line. It's about half as fast as Linux during boot now,
visibly slower post-boot.
Jan
next prev parent reply other threads:[~2007-07-17 9:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 8:18 early_cpu_init() and identify_cpu() Jan Beulich
2007-07-17 7:50 ` Keir Fraser
2007-07-17 9:58 ` Jan Beulich [this message]
2007-07-17 10:05 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2007-07-13 16:16 Jan Beulich
2007-07-13 16:26 ` Keir Fraser
2007-07-16 6:14 ` Jan Beulich
2007-07-16 6:25 ` Keir Fraser
2007-07-16 6:41 ` Jan Beulich
2007-07-16 6:57 ` Keir Fraser
2007-07-16 7:01 ` Keir Fraser
2007-07-16 7:31 ` Jan Beulich
2007-07-16 7:30 ` Jan Beulich
2007-07-16 9:23 ` Alan Cox
2007-07-17 7:55 ` Keir Fraser
2007-07-17 10:00 ` Jan Beulich
2007-07-17 10:15 ` Keir Fraser
2007-07-17 10:23 ` Keir Fraser
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=469CAEEF.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=keir@xensource.com \
--cc=xen-devel@lists.xensource.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 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.