All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Automagic command loading
Date: Wed, 29 Sep 2004 22:00:01 +0000	[thread overview]
Message-ID: <877jqcn3by.fsf@marco.marco-g.com> (raw)
In-Reply-To: <20040929213801.GC30478@artax.karlin.mff.cuni.cz> (Tomas Ebenlendr's message of "Wed, 29 Sep 2004 23:38:01 +0200")

Tomas Ebenlendr <ebik@artax.karlin.mff.cuni.cz> writes:

> Disadvantage: current solution slowly reads the contens of directory.
> This is probably caused by opening files by /full/ path, where we
> principially have opened directory (and resolved path to it.).

Isn't it that slow because the *entire* ELF is read into memory?

> Not so disadvanyage because:
> 1.) this solution caches the contents of directory in $prefix. So it is
> slow only when inserting autocmd or after $prefix is changed. (or user
> executed cache_autocommands - now i think the caching at insert of module
> is misfeature. User can use cache_autocommands manually).

So how should it work in your opinion?  I think it should not cache
everything at startup.  It should look for "ls.mod" when you run
"ls".  If it can not be found it should try all modules until "ls" was
found.  The cache is filled automatically.

> 2.) Latency was under bochs on slow (P300) machine.
>
> You can always turn it off by not inserting module autocmd.

Or use another autoloader if I understand things correctly.

--
Marco




  reply	other threads:[~2004-09-29 22:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 19:05 Automagic command loading Tomas Ebenlendr
2004-09-29 12:16 ` Marco Gerards
2004-09-29 22:14   ` Tomas Ebenlendr
2004-09-29 15:02 ` Yoshinori K. Okuji
2004-09-29 21:38   ` Tomas Ebenlendr
2004-09-29 22:00     ` Marco Gerards [this message]
2004-09-29 22:23       ` Tomas Ebenlendr
2004-09-30 13:33     ` Yoshinori K. Okuji
2004-09-30 15:05       ` Marco Gerards
2004-09-30 17:44         ` Tomas Ebenlendr
2004-10-01 15:09         ` Yoshinori K. Okuji
2004-10-01 15:36           ` chaac
2004-10-01 21:56           ` Tomas Ebenlendr
2004-10-06  8:43             ` Yoshinori K. Okuji

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=877jqcn3by.fsf@marco.marco-g.com \
    --to=metgerards@student.han.nl \
    --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.