From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: grub2 uefi disk cache
Date: Wed, 09 Jun 2010 21:16:49 +0200 [thread overview]
Message-ID: <4C0FE8A1.6080806@gmail.com> (raw)
In-Reply-To: <AANLkTilKs-ThT8cpNJfu5bKcemDsQEopIGI_o-w5ujyK@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
On 06/08/2010 03:24 PM, KESHAV P.R. wrote:
> Is this change needed? I have about 4-5 sec gap between "Welcome to
> GRUB" and the GRUB2 boot menu in UEFI x86_64.
>
>
There is no reason for making this platform-specific. I once made a
patch which scales cache in proportion to available free memory.
http://lists.gnu.org/archive/html/grub-devel/2009-03/msg00143.html
That patch increased core size and it wasn't ever proved that it results
in measurable boot time decrease. If you benchmark the patch and provide
the results that patch can be applied.
Also some (U)EFI implementations have a following bug: they take very
long time to read sector if you do too much read in the row. I suppose
it doesn't respect some kind of HD timings and operation request isn't
accepted by hardware and so EFI waits till it timeouts to notice it.
On such EFI implementations, adding grub_millisleep to grub_efidisk_read
makes it work faster
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2010-06-09 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 13:24 grub2 uefi disk cache KESHAV P.R.
2010-06-09 19:16 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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=4C0FE8A1.6080806@gmail.com \
--to=phcoder@gmail.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.