From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Image scaling performance
Date: Thu, 26 Feb 2015 18:16:17 +0100 [thread overview]
Message-ID: <54EF54E1.5050109@gmail.com> (raw)
In-Reply-To: <CAN9vWD+DVxgwVQpDx5bAgsrokpO6XKTMxUe4sEOUAN8W1oRKfQ@mail.gmail.com>
On 26.02.2015 18:10, Michael Zimmermann wrote:
> Is there a way to create a performance profile so I can see what
> exactly needs so much time? I don't have JTAG but maybe UART+GDB could
> help with that.
>
Have a look at boot_time.
> adding prints is kind of annoying :D
>
> On Thu, Feb 26, 2015 at 5:44 PM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder@gmail.com> wrote:
>> On 25.02.2015 19:46, Michael Zimmermann wrote:
>>>
>>> I'm still questioning the efficiency
>>> math operations because on slow devices there are other bottlenecks of
>>> the same kind(like de/compression).
>>
>> That's pure speculation at that point. GRUB has 3 compression algorithms:
>> - minilzo. Has some divisions in parts which GRUB doesn't use. Those parts
>> are easily disablable and I'll just do so.
>> - gzip. Uses division only in zlib header check. I'll optimise it a little
>> but it's only one division in header check, not in compressed data body.
>> - xz. No divisions
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
next prev parent reply other threads:[~2015-02-26 17:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 9:39 Image scaling performance Michael Zimmermann
2015-02-24 9:51 ` Vladimir 'phcoder' Serbinenko
2015-02-24 10:00 ` Michael Zimmermann
2015-02-24 11:27 ` Vladimir 'phcoder' Serbinenko
2015-02-24 11:47 ` Michael Zimmermann
2015-02-24 12:39 ` Vladimir 'phcoder' Serbinenko
2015-02-24 18:01 ` Michael Zimmermann
2015-02-24 18:22 ` Andrei Borzenkov
2015-02-25 16:20 ` Leif Lindholm
2015-02-25 15:45 ` Leif Lindholm
2015-02-25 16:23 ` Leif Lindholm
2015-02-25 18:38 ` Michael Zimmermann
2015-02-25 18:41 ` Vladimir 'phcoder' Serbinenko
2015-02-25 18:46 ` Michael Zimmermann
2015-02-25 18:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-02-25 19:28 ` Michael Zimmermann
2015-02-25 20:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-02-25 20:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-02-25 20:54 ` Michael Zimmermann
2015-02-26 16:44 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-02-26 17:10 ` Michael Zimmermann
2015-02-26 17:16 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2015-02-26 20:27 ` Michael Zimmermann
2015-02-26 20:35 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=54EF54E1.5050109@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.