All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] make search faster by first trying without module autoloading
Date: Mon, 17 Aug 2009 16:07:51 +0200	[thread overview]
Message-ID: <20090817140751.GQ32551@thorin> (raw)
In-Reply-To: <d7ead6de0908170646s13b0532ge25cf1bc966822f6@mail.gmail.com>

On Mon, Aug 17, 2009 at 03:46:40PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Mon, Aug 17, 2009 at 3:32 PM, Robert Millan<rmh@aybabtu.com> wrote:
> > On Fri, Aug 14, 2009 at 05:58:20PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> >> Hello. When search encounters an unknown filesystem or filesystem
> >> without partition it triggers fs module autoload which takes
> >> noticeable time. To improve the situation I propose (after discussing
> >> with Robert Millan) to first search without autoloading modules if we
> >> need to find only one device (with --set ) and retry with autoloading
> >> if without autoloading the search failed. Additionally I modify
> >> grub-mkconfig to load correct module manually before issuing search to
> >> decrease booting time if filesystem is different that our boot one.
> >
> > Looks good to me.  Also, I think Yves suggestion is a good idea.
> >
> In this case 'var' stands for a 'variable' which is sensible in this
> case since it's environment variable name.

Ah, ok.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      reply	other threads:[~2009-08-17 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 15:58 [PATCH] make search faster by first trying without module autoloading Vladimir 'phcoder' Serbinenko
2009-08-15  7:29 ` Yves Blusseau
2009-08-17 13:32 ` Robert Millan
2009-08-17 13:46   ` Vladimir 'phcoder' Serbinenko
2009-08-17 14:07     ` Robert Millan [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=20090817140751.GQ32551@thorin \
    --to=rmh@aybabtu.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.