All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin D Bennett <colin@gibibit.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: cjwatson@ubuntu.com
Subject: Re: [RFC] Hacky MTRR support
Date: Mon, 28 Jun 2010 09:40:21 -0700	[thread overview]
Message-ID: <20100628094021.77b3667f@svelte> (raw)
In-Reply-To: <20100625085834.GM21862@riva.ucam.org>

On Fri, 25 Jun 2010 09:58:34 +0100
Colin Watson <cjwatson@ubuntu.com> wrote:

> I recently posted ("Subject: [PATCH] Optimise memset on i386" -
> sorry, I don't seem to have a route to lists.gnu.org at the moment so
> I can't post an archive link) about optimising GRUB's video
> initialisation, and hinted that it might be possible to do better by
> implementing MTRRs as well in order to allow the system to combine
> writes to video memory rather than taking a cache stall for every
> single write.  I can report that, at least on the hardware I was
> using, it does make a significant difference: filling the screen with
> solid colour now takes 10 milliseconds rather than 160!  This ended
> up shaving about a second off the boot time of the project I'm
> working on.

In addition to the improved startup speed, I see the potential for a
huge increase in graphical menu responsiveness if caching is enabled.
Would framebuffer draw and image blitting performance be improved by
using write-combining with MTRRs?

Regards,
Colin


  parent reply	other threads:[~2010-06-28 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25  8:58 [RFC] Hacky MTRR support Colin Watson
2010-06-28  9:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-06-28 16:40 ` Colin D Bennett [this message]
2010-06-28 16:55   ` Colin Watson
2010-06-28 17:32   ` Seth Goldberg

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=20100628094021.77b3667f@svelte \
    --to=colin@gibibit.com \
    --cc=cjwatson@ubuntu.com \
    --cc=grub-devel@gnu.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.