All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niv Sardi <xaiki@cxhome.ath.cx>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [RFC, patch 1/2] Allow up to 1GB logs in mkfs.xfs
Date: Fri, 22 Feb 2008 13:44:38 +1100	[thread overview]
Message-ID: <ncctzk11zhl.fsf@sgi.com> (raw)
In-Reply-To: <20080221230833.GG155407@sgi.com> (David Chinner's message of "Fri, 22 Feb 2008 10:08:34 +1100")

David Chinner <dgc@sgi.com> writes:

> Increase the maximum log size supported by mkfs.
>
> The log size can be increased easily in mkfs by changing a few
> defines and a couple of types to allow the log size to increase to
> 1GB. Theoretically, the log size can be made much, much larger than
> this (up to 2^32 sectors), but going beyond 2^30 *bytes* causes
> integer overflow issues in the kernel log code.
>
> e.g. a 2GB log (2^31 bytes) will not mount because the
> space calculations in the kernel use "int" types and
> overflow:
>
> STATIC int
> xlog_space_left(xlog_t *log, int cycle, int bytes)
>
> Hence logs larger than 2^30 will not work without kernel
> modifications.  Therefore this change is limited to increasing the
> log size to what we can currently support in kernel space with
> needing kernel modifications.

I'm glad you got time to get around this, I didn't include it in the
first batch as I was told it 'broke things'.

Looks good to me.

Cheers,
-- 
Niv Sardi

  reply	other threads:[~2008-02-22  2:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 23:08 [RFC, patch 1/2] Allow up to 1GB logs in mkfs.xfs David Chinner
2008-02-22  2:44 ` Niv Sardi [this message]
2008-02-22  5:03   ` David Chinner
2008-02-22  5:44     ` Lachlan McIlroy
2008-02-22  6:53       ` David Chinner
2008-02-25  1:10         ` Mark Goodwin
2008-02-25  1:31           ` Lachlan McIlroy
2008-02-28 18:17             ` David 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=ncctzk11zhl.fsf@sgi.com \
    --to=xaiki@cxhome.ath.cx \
    --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 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.