From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] btree support in xfs driver
Date: Fri, 01 Feb 2008 17:55:34 +0100 [thread overview]
Message-ID: <87r6fwehvd.fsf@xs4all.nl> (raw)
In-Reply-To: <ca0f59980802010509y6dd2f82bm6df3896e9a5e0b2f@mail.gmail.com> (bean123ch@gmail.com's message of "Fri, 1 Feb 2008 21:09:50 +0800")
Bean <bean123ch@gmail.com> writes:
Hi!
> change in this new patch:
>
> Fix small bug in xfs
> Fix a bug in fshelp
> Define NESTED_FUNC_ATTR as regparm(1) and us it for call_hook.
>
> With this patch, i'm able to load a highly sparse file about 200M.
>
>
> 2008-02-01 Bean <bean123ch@gmail.com>
>
> * fs/xfs.c (grub_xfs_sblock): New member log2_dirblk.
> (grub_xfs_btree_node): New structure.
> (grub_xfs_btree_root): New structure.
> (grub_xfs_inode): New members nblocks, extsize, nextents and btree.
> (GRUB_XFS_EXTENT_OFFSET): Use exts instead of inode->data.extents.
> (GRUB_XFS_EXTENT_BLOCK): Likewise.
> (GRUB_XFS_EXTENT_SIZE): Likewise.
> (grub_xfs_read_block): Support btree format type.
> (grub_xfs_iterate_dir): Use NESTED_FUNC_ATTR in call_hook.
> Use directory block as basic unit.
>
> * fs/fshelp.c (grub_fshelp_read_file): Bug fix for sparse block.
>
> * aclocal.m4 (grub_i386_CHECK_REGPARM_BUG): Define NESTED_FUNC_ATTR as
> __attribute__ ((__regparm__ (1))).
Looks fine to me! :-)
--
Marco
next prev parent reply other threads:[~2008-02-01 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 19:40 [PATCH] btree support in xfs driver Bean
2008-01-31 19:57 ` Marco Gerards
2008-02-01 3:31 ` Bean
2008-02-01 5:44 ` Marco Gerards
2008-02-01 13:09 ` Bean
2008-02-01 16:55 ` Marco Gerards [this message]
2008-02-02 14:16 ` Bean
2008-01-31 19:58 ` 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=87r6fwehvd.fsf@xs4all.nl \
--to=mgerards@xs4all.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.