From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] disk/fs_uuid.c
Date: Fri, 4 Jul 2008 00:50:21 +0200 [thread overview]
Message-ID: <20080703225021.GA4074@thorin> (raw)
In-Reply-To: <87prpu4wkt.fsf@xs4all.nl>
On Thu, Jul 03, 2008 at 09:05:54PM +0200, Marco Gerards wrote:
> Robert Millan <rmh@aybabtu.com> writes:
>
> > This disk driver allows access to partitions that contain a filesystem with
> > known UUID via "(UUID=xxxxxxx)" syntax.
> >
> > The iterator is unimplemented on purpose, because it makes the code smaller
> > and it isn't useful to waste time inspecting the same devices twice while
> > scanning for LVM / whatsoever.
> >
> > Also note that as it currently stands it is highly inefficient. I can't
> > understand why; new UUIDs are searched everytime on each open() call, but
> > this shouldn't be much of an issue since we have a disk cache in kernel to
> > make that efficient. At least, it isn't e.g. for grub_fs_probe() which is
> > called multiple times.
> >
> > Even with this efficiency problem, since it doesn't interfere with anything
> > else I'm inclined to commit it, if nobody objects.
>
> Why didn't you just extend the search command? I think that would be
> favorable.
I _did_ extend the search command (before this patch). The reason for
providing this is basicaly that it makes grub.cfg more readable (and easier
to understand), and can't be used outside the context of scripting (for
example, to set your root/prefix to it, but that would require a patch I
intend to put together soon).
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-07-03 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 16:23 [PATCH] disk/fs_uuid.c Robert Millan
2008-06-26 14:26 ` Robert Millan
2008-07-03 19:05 ` Marco Gerards
2008-07-03 22:50 ` Robert Millan [this message]
2008-07-03 23:06 ` Robert Millan
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=20080703225021.GA4074@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.