From: Christoph Hellwig <hch@infradead.org>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [patch] allow mkfs to make larger logs
Date: Thu, 22 May 2008 09:23:33 -0400 [thread overview]
Message-ID: <20080522132333.GB4972@infradead.org> (raw)
In-Reply-To: <20080522061222.GQ173056135@sgi.com>
On Thu, May 22, 2008 at 04:12:22PM +1000, David Chinner wrote:
> ===================================================================
> --- xfs-cmds.orig/xfsprogs/include/xfs_fs.h 2008-05-15 16:32:52.929462025 +1000
> +++ xfs-cmds/xfsprogs/include/xfs_fs.h 2008-05-15 18:50:19.494520368 +1000
> @@ -248,10 +248,13 @@ typedef struct xfs_fsop_resblks {
> * Minimum and maximum sizes need for growth checks
> */
> #define XFS_MIN_AG_BLOCKS 64
> -#define XFS_MIN_LOG_BLOCKS 512
> -#define XFS_MAX_LOG_BLOCKS (64 * 1024)
> -#define XFS_MIN_LOG_BYTES (256 * 1024)
> -#define XFS_MAX_LOG_BYTES (128 * 1024 * 1024)
> +#define XFS_MIN_LOG_BLOCKS 512ULL
> +#define XFS_MAX_LOG_BLOCKS (1024 * 1024ULL)
> +#define XFS_MIN_LOG_BYTES (10 * 1024 * 1024ULL)
> +
> +/* keep the maximum size under 2^31 by a small amount */
> +#define XFS_MAX_LOG_BYTES \
> + ((2 * 1024 * 1024 * 1024ULL) - XFS_MIN_LOG_BYTES)
This file is a copy for the kernel, so please update it there aswell,
once we get changes to these files in both xfs-cmds and the kernel tree
merging will become a complete nightmare.
Except for that the patch looks good to me.
next prev parent reply other threads:[~2008-05-22 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 6:12 [patch] allow mkfs to make larger logs David Chinner
2008-05-22 13:23 ` Christoph Hellwig [this message]
2009-05-10 19:35 ` Christoph Hellwig
2008-07-10 22:44 ` Dave Chinner
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=20080522132333.GB4972@infradead.org \
--to=hch@infradead.org \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox