All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: ReiserFS reading performance patch
Date: Fri, 27 Apr 2012 20:36:29 +0200	[thread overview]
Message-ID: <4F9AE72D.5010800@gmail.com> (raw)
In-Reply-To: <CAO1Q+jcf-aQZ704GCoJYvWnM3gyssB9aZwtnRJWEp4VC8T3W3A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 767 bytes --]

On 27.04.2012 16:05, Albert Zeyer wrote:
> * Write a simplified compile.py script.
We don't have any compile.py.
> * Remove nested functions. They don't work on Mac because of stack
> execution protection.
It can be disabled. It's Apple fault for not allowing to disable it
selectively. Replacing nested functions is possible if done properly but
the "let's make it all static" is wrong and will create problems with
recursion, i.a. with nested partitions.
> * Improve ReiserFS reading performance.
This is interesting. I was aware of the performance problem but have
never really digged into it.
C++ is a no-go for GRUB since libstdc++ by itself would be bigger than
our leniest size limits.

-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2012-04-27 18:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 14:05 ReiserFS reading performance patch Albert Zeyer
2012-04-27 18:36 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-04-27 20:31   ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-04-28 10:06     ` Bean
2012-04-28 11:08       ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-01 17:59 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-01 18:16   ` 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=4F9AE72D.5010800@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.